Findings

CVE-2026-64020

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.

Published Jul 19, 2026 · updated Oct 15, 2026 · linux linux kernel

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.

Code

The project this record applies to. Exploit listings stay in References.

Timeline

Detection, updates, and resolution for this record.

  1. Jul 19, 2026 · NIST NVD

    Detected

    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.

  2. Oct 15, 2026 · NIST NVD

    Updated

    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.

Affected

  • cpe linux/linux kernelversion unspecified
  • cpe linux/linux kernel7.1

Sources

  • CVE.orgVulnerability recordCVE-2026-64020

    Official CVE identifier

    cve.org
  • FIRST EPSSExploitation probabilityCVE-2026-64020

    30-day exploitation probability 0.5%

    first.org
  • NIST NVDVulnerability recordCVE-2026-64020

    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.

    nvd.nist.gov

References

CVE-2026-64020 · ZeroDay Findings