CVE-2026-64320
Pre-auth nvmet OOB heap read leaks kernel memory and can crash Linux hosts.
Is CVE-2026-64320 being exploited?
Not confirmed. CVE-2026-64320 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.75% probability of exploitation in the next 30 days.
How severe is CVE-2026-64320?
CVE-2026-64320 is rated Critical with a CVSS score of 9.1. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-64320?
Yes. A fix has been recorded for CVE-2026-64320. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-64320 affect?
CVE-2026-64320 affects Linux kernel (nvmet subsystem), NVMe-oF targets (nvmet-tcp, nvmet-rdma, nvmet-fc), Systems exposing NVMe over Fabrics to untrusted networks. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-64320?
Install vendor kernel security update, restrict/block NVMe-oF access, firewall NVMe target ports.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Unauthenticated remote attacker can trigger out-of-bounds heap read via nvmet Discovery Get Log Page, disclosing kernel memory (pointers) and causing kernel panic/DoS; aids ASLR bypass.
Immediate action required
- affected>= a07b4970f464f13640e28e16dad6cfa33647cc99 and < 33b974eb626154ae9348f2bac7de84cb2a3d9dd4
- affected>= a07b4970f464f13640e28e16dad6cfa33647cc99 and < 56c021a0869260d04c4b65d1471936aaf9177114
- affected>= a07b4970f464f13640e28e16dad6cfa33647cc99 and < a29b316b9bbfd269f323ab4ba9906a894025680f
- affected>= a07b4970f464f13640e28e16dad6cfa33647cc99 and < 53cd102a7a56079b11b897835bd9b94c14e6322c
- affected4.8
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.