CVE-2026-64071·Kernel vulnerability
In the Linux kernel, the following vulnerability has been resolved: nvme-pci: fix use-after-free in nvme_free_host_mem() nvme_free_host_mem() frees dev->hmb_sgt via dma_free_noncontiguous() but never clears the pointer afterward. This leads to a use-after-free if nvme_free_host_mem() is called twice in the same error path. This can happen during nvme_probe() when nvme_setup_host_mem() succeeds in allocating the HMB (setting dev->hmb_sgt) but nvme_set_host_mem() fails with an I/O error: nvme_setup_host_mem() nvme_alloc_host_mem_single() -> sets dev->hmb_sgt nvme_set_host_mem() -> fails with -EIO nvme_free_host_mem() -> frees hmb_sgt, but does NOT NULL it return error nvme_probe() error path: nvme_free_host_mem() -> dev->hmb_sgt is stale, use-after-free The second call dereferences the freed sgt, causing a NULL pointer dereference in iommu_dma_free_noncontiguous() when it accesses sgt->sgl->dma_address (the backing memory has been freed and zeroed). This is reproducible on Thunderbolt-attached NVMe devices (e.g., OWC Envoy Express behind a Dell WD22TB4 dock) where the device intermittently returns I/O errors during HMB setup due to PCIe link instability. BUG: kernel NULL pointer dereference, address: 0000000000000010 RIP: 0010:iommu_dma_free_noncontiguous+0x22/0x80 Call Trace: <TASK> dma_free_noncontiguous+0x3b/0x130 nvme_free_host_mem+0x30/0xf0 [nvme] nvme_probe.cold+0xcc/0x275 [nvme] local_pci_probe+0x43/0xa0 pci_device_probe+0xeea/0x290 really_probe+0xf9/0x3b0 __driver_probe_device+0x8b/0x170 driver_probe_device+0x24/0xd0 __driver_attach_async_helper+0x6b/0x110 async_run_entry_fn+0x37/0x170 process_one_work+0x1ac/0x3d0 worker_thread+0x1b8/0x360 kthread+0xf7/0x130 ret_from_fork+0x2d8/0x3a0 ret_from_fork_asm+0x1a/0x30 </TASK> Fix this by setting dev->hmb_sgt to NULL after freeing it, so the second call takes the multi-descriptor path which safely handles the already-cleaned-up state.
- Severity
- high
- Software
- Kernel
- Fixed in
- 7.0.11
- Published
How likely is exploitation
FIRST's Exploit Prediction Scoring System puts the probability of this CVE being exploited in the next 30 days at 0.13% — higher than 2% of all published CVEs. EPSS is an independent forecast of exploitation, not a severity rating: it says nothing about how much damage a successful attack does, which is what a CVSS score measures.
Read the two together. CVE-2026-64071 scores 7.8 on CVSS, so a successful attack would be serious — but at 0.13%, almost nobody is currently attempting it. That is a different situation from a flaw under mass exploitation, and it is usually the difference between patching on your next maintenance window and patching tonight.
Affected versions
From: 6.19
Until: 7.0.11
Fixed in: 7.0.11
How to fix this CVE
Update your Linux kernel to version 7.0.11 or later to resolve a use-after-free vulnerability in NVMe PCI driver memory handling. This issue can cause system crashes when NVMe host memory buffer allocation fails during device initialization. Apply the kernel update and reboot your system to fully remediate the vulnerability.
sudo dnf update kernelDefensia detects this vulnerability
How to check if you are affected
- Check your kernel version: uname -r
- Verify if NVMe devices are present: lspci | grep -i nvme
- Review kernel logs for NVMe initialization errors: dmesg | grep -i nvme
- Confirm the patch: grep -i 'hmb_sgt' /boot/config-$(uname -r) or check if kernel version is >= 7.0.11
FAQ
What is CVE-2026-64071?
This is a use-after-free vulnerability in the Linux kernel's NVMe PCI driver that occurs when host memory buffer allocation fails during device initialization, potentially leading to a NULL pointer dereference and system crash.
Is CVE-2026-64071 being actively exploited?
No, this vulnerability is not listed in CISA's Known Exploited Vulnerabilities (KEV) catalog and no public exploits are available. It primarily affects Thunderbolt-attached NVMe devices experiencing initialization failures.
What versions of Kernel are affected by CVE-2026-64071?
Linux kernel versions 6.19 through 7.0.10 are affected. The vulnerability was fixed in kernel version 7.0.11.
How do I check if my server is vulnerable to CVE-2026-64071?
Run 'uname -r' to check your kernel version. If it shows 6.19 through 7.0.10, your system is vulnerable. Additionally, verify NVMe device presence with 'lspci | grep -i nvme'.
Does Defensia detect CVE-2026-64071?
Yes — Defensia's CVE advisory scanner compares installed package versions against the NVD database. If Linux kernel is installed on a monitored server, CVE-2026-64071 will appear in your dashboard with remediation steps.
Related Kernel CVEs
References
Track CVEs across your fleet automatically
Defensia scans your Linux servers and tells you exactly which ones are running vulnerable versions — including CVE-2026-64071. Free for 1 server.
Get started free