Menu

Star on GitHub · 3.2k

CVE-2026-64019

In the Linux kernel, the following vulnerability has been resolved: nvme-pci: fix dma mapping leak on data setup error We're leaking the initial DMA mapping during iteration if we fail to allocat…

Published Jul 19, 2026EPSS 0.16%

Overview

CVE-2026-64019 is a known-severity vulnerability. It was published on July 19, 2026.

Technical description

In the Linux kernel, the following vulnerability has been resolved:

nvme-pci: fix dma mapping leak on data setup error

We're leaking the initial DMA mapping during iteration if we fail to

allocate the tracking descriptor for both PRP and SGL. Unmap the

iterator directly; we can't use the existing unmap helper because it

depends on the tracking descriptor being successfully allocated, so a

new one for an in-use iterator is provided.

The mappings were also leaking when the driver detects an invalid

bio_vec when mapping PRPs, so fix that too.

Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

Frequently asked questions

What is CVE-2026-64019?

CVE-2026-64019 is a known-severity vulnerability. It was published on July 19, 2026.

How severe is CVE-2026-64019?

CVSS score information is not yet available for this vulnerability. Check back as the CVE record is updated by NVD analysts.

How do I fix or remediate CVE-2026-64019?

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2026-64019?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2026-64019 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.