CVE-2026-72130
Heap out-of-bounds write in Linux nvmet-auth via crafted AUTH_RECEIVE (NVMe-oF).
Is CVE-2026-72130 being exploited?
Not confirmed. CVE-2026-72130 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-72130?
CVE-2026-72130 is rated Critical. 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-72130?
Yes. A fix has been recorded for CVE-2026-72130. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-72130 affect?
CVE-2026-72130 affects Linux kernel (nvmet module), NVMe-oF targets with in-band DH-HMAC-CHAP authentication, Storage systems using Linux nvmet. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-72130?
Apply vendor Linux kernel updates or backports; disable in-band DH-HMAC-CHAP if patching delayed.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Remote 16-byte heap OOB write via NVMe-oF auth leading to kernel memory corruption, possible kernel crash or remote code execution.
Immediate action required
- affected>= db1312dd95488b5e6ff362ff66fcf953a46b1821 and < 80bf7b7f676e3987bbe06af3c359bd56ac91a5a9
- affected>= db1312dd95488b5e6ff362ff66fcf953a46b1821 and < 2eaa3ad450141cfcf187bb43cb8335eb336b5f87
- affected>= db1312dd95488b5e6ff362ff66fcf953a46b1821 and < bc111698b46e43eddd8664cceaa621cd559e99a0
- affected>= db1312dd95488b5e6ff362ff66fcf953a46b1821 and < 779575bc35c687697ba69e904f2cd22e60112534
- affected6.0
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.