Skip to content
Systems

CVE-2026-64319

9.1
Critical
EPSS 0.52%Patch availableJul 27, 2026

Linux kernel nvmet-auth OOB heap read via crafted NVMe-oF DHCHAP_REPLY

common questions

Is CVE-2026-64319 being exploited?

Not confirmed. CVE-2026-64319 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.52% probability of exploitation in the next 30 days.

How severe is CVE-2026-64319?

CVE-2026-64319 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-64319?

Yes. A fix has been recorded for CVE-2026-64319. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-64319 affect?

CVE-2026-64319 affects Linux kernel nvmet (NVMe-oF target) with nvmet-auth, Linux distributions with nvmet-auth/DHCHAP enabled, Storage systems using Linux-based NVMe-oF targets. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-64319?

Apply kernel/security updates; restrict NVMe-oF access or disable nvmet-auth until patched

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
Linux kernel nvmet (NVMe-oF target) with nvmet-authLinux distributions with nvmet-auth/DHCHAP enabledStorage systems using Linux-based NVMe-oF targets
impact

Pre-auth remote out-of-bounds heap read in nvmet-auth via crafted DHCHAP_REPLY; may leak kernel memory and cause DoS (information disclosure, instability).

action required

Patch when possible

affected versions
Linux Linux
  • affected>= db1312dd95488b5e6ff362ff66fcf953a46b1821 and < 80cd28b56ab62d3e7ed0a7bf05282e6d3ee5b2a0
  • affected>= db1312dd95488b5e6ff362ff66fcf953a46b1821 and < 999f6205ede984a786f35f727b01f971b98e215d
  • affected>= db1312dd95488b5e6ff362ff66fcf953a46b1821 and < 6d7649c1231dac14d906985d2936967e23041c26
  • affected>= db1312dd95488b5e6ff362ff66fcf953a46b1821 and < caa71b3a43ea5c13fe7141cb019ebcb03b8ac857
  • affected>= db1312dd95488b5e6ff362ff66fcf953a46b1821 and < 3a413ece2504c70aa34a20be4dafec04e8c741f9
  • affected6.0
vendor says fixed in< 6.0, >= 6.6.145 and <= 6.6.*, >= 6.12.96 and <= 6.12.*, >= 6.18.39 and <= 6.18.*, >= 7.1.4 and <= 7.1.*, >= 7.2 and <= *

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.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free