CVE-2026-64232
Linux kernel block-layer integrity-segment bug can crash hosts and enable kernel-level compromise.
Is CVE-2026-64232 being exploited?
Not confirmed. CVE-2026-64232 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.46% probability of exploitation in the next 30 days.
How severe is CVE-2026-64232?
CVE-2026-64232 is rated Critical with a CVSS score of 9.8. 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-64232?
Yes. A fix has been recorded for CVE-2026-64232. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-64232 affect?
CVE-2026-64232 affects Linux kernel (blk-mq), dm-multipath, nvme-rdma, NVMe-oF targets, and 1 further product or version. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-64232?
Apply vendor Linux kernel updates for blk-mq/driver fixes and reboot affected hosts immediately.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
BUG_ON during block request dispatch causing kernel panic/DoS; may enable kernel code execution in stacked block driver setups.
Immediate action required
- affected>= 76c313f658d2752e8527610677164aa7094ef7a5 and < 53a01bcc0242590eda4c452a5bd996f62457113b
- affected>= 76c313f658d2752e8527610677164aa7094ef7a5 and < 0943f81e1b3176f27dbaf6db268fc69d8a94f0ba
- affected>= 76c313f658d2752e8527610677164aa7094ef7a5 and < 42929c98d044f126508baf54a65b0f87f932fa75
- affected>= 76c313f658d2752e8527610677164aa7094ef7a5 and < 2c6e6a18a37b905cb584eb0dda3ae482162a81ca
- affected6.12
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.