CVE-2026-64020: Linux kernel · nvme-pci: fix dma_vecs leak on p2p memory
Source GCVE Database
Not known to be exploited · CVSS 7.5 High.
Data as of 26 Oct 2026, 17:16 UTC
- EPSS
- 0.6% chance of exploitation in 30 days – higher than 48% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/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 has been implemented in the Linux kernel to address this vulnerability. Users should update their Linux kernel to a version that includes this fix. Patch status is not explicitly stated in the provided data; therefore, check the official Linux kernel advisories or vendor updates for the exact fixed versions and apply the update accordingly.
Description
In the Linux kernel, the following vulnerability has been resolved: nvme-pci: fix dma_vecs leak on p2p memory We don't unmap P2P memory, so we don't need to track it. The dma_vec allocation was getting leaked on the completion.
References
- nvd.nist.gov/vuln/detail/CVE-2026-64020 (opens in a new tab)
- git.kernel.org/stable/c/24ea0de233d9ebb5ebd6f6018eaf2084af25e3dd (opens in a new tab)
- git.kernel.org/stable/c/85686c72966c5ee637893f124ddb31a1cace7bee (opens in a new tab)
- git.kernel.org/stable/c/b9390aa62fdcabdaac2d09545be05901f6cecaf5 (opens in a new tab)