CVE-2026-64019: Linux kernel · nvme-pci: fix dma mapping leak on data setup error
Source GCVE Database
Not known to be exploited · CVSS 5.5 Medium.
Data as of 26 Oct 2026, 13:47 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 5% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 19 Jul 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
AI-suggested
A fix for this vulnerability has been implemented in the Linux kernel. Users should apply the official kernel updates that include this patch to resolve the DMA mapping leak. Since this is a kernel-level fix, upgrading to a patched kernel version is the recommended remediation. Patch status is not explicitly confirmed in the provided data; therefore, check the official Linux kernel advisories for the exact fixed versions and update accordingly.
Description
A vulnerability in the Linux kernel's nvme-pci driver caused a DMA mapping leak during data setup errors. The issue occurs when the driver fails to allocate a tracking descriptor for PRP and SGL mappings, leading to unreleased DMA mappings. Additionally, mappings leaked when invalid bio_vec structures were detected during PRP mapping. This vulnerability has been resolved by introducing a new unmap method that handles in-use iterators without relying on the tracking descriptor.