Quick answers
- Is CVE-2026-64320 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-64320 being exploited in the wild.
- How severe is CVE-2026-64320?
- Informational severity, with a CVSS score of 8.2, published 25 July 2026.
- Which products and versions are affected?
- Linux Kernel a07b4970f464 to 33b974eb6261.
- Is there a fix for CVE-2026-64320?
- A patch was published on 2026-07-18: Fix committed to stable kernel trees Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-64320 attacked?
- It is attacked over the network, in an operating system.
- Am I affected by CVE-2026-64320?
- Check whether you run Linux Kernel at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
An out-of-bounds heap read exists in nvmet_execute_disc_get_log_page() within the Linux kernel's NVMe target (nvmet) implementation. The function fails to validate the host-supplied 64-bit Log Page Offset (lpo) against the size of the allocated buffer. Because the Discovery controller is unauthenticated, any network peer (TCP/RDMA/FC) can provide a large offset to read adjacent kernel heap memory or trigger a kernel panic by accessing unmapped memory. Attackers can leak sensitive kernel pointers or cause a denial-of-service. The issue has been resolved by validating the offset against the log page size and capping the copy length.
Affected products
- Linux Linux Kernel a07b4970f464 to 33b974eb6261
Timeline
- 2026-05-27: other: Vulnerability reported by researcher
- 2026-07-18: patched: Fix committed to stable kernel trees
- 2026-07-25: disclosed: CVE published