Widespread Linux kernel vulnerability in NTFS driver with 9.8 CVSS; can disrupt systems and enable kernel compromise—impacts many organizations using Linux.
CVE-2026-89612
NTFS boot-sector parse bug allows kernel OOB via crafted NTFS volumes
Is CVE-2026-89612 being exploited?
Not confirmed. CVE-2026-89612 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.55% probability of exploitation in the next 30 days.
How severe is CVE-2026-89612?
CVE-2026-89612 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-89612?
Yes. A fix has been recorded for CVE-2026-89612. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-89612 affect?
CVE-2026-89612 affects Linux kernel NTFS driver (parse_ntfs_boot_sector), Affected Linux distributions prior to Sept 2026 stable kernel fixes. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-89612?
Apply vendor kernel updates immediately; avoid mounting untrusted NTFS volumes.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Mounting a crafted NTFS volume can trigger kernel out-of-bounds access, causing crashes or local privilege escalation and potential kernel compromise.
Immediate action required
- affected>= 11ccc9107dc460de28af90fac1f42404d9802735 and < 8f8420b68a6f05ca2b03779d8208814ec539b9e5
- affected>= 11ccc9107dc460de28af90fac1f42404d9802735 and < cc9d09fef78410bcd37ac05168cbd5f6dd75d3d2
- affected7.1
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.