Affects the Linux kernel (core OS component) with high CVSS; impacts any org using Linux—widespread, infrastructure-level risk.
CVE-2026-72206
Linux ntfs INDX header validation flaw allows kernel memory corruption.
Is CVE-2026-72206 being exploited?
Not confirmed. CVE-2026-72206 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-72206?
CVE-2026-72206 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-72206?
Yes. A fix has been recorded for CVE-2026-72206. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-72206 affect?
CVE-2026-72206 affects Linux kernel (ntfs subsystem), All Linux distributions using vulnerable kernels, Systems that mount or parse NTFS volumes or images. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-72206?
Upgrade to vendor-fixed kernel ASAP; avoid mounting untrusted NTFS media.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Malformed NTFS INDX blocks can cause kernel memory corruption, crashes, and may enable privilege escalation or remote code execution when mounting/reading malicious NTFS volumes.
Patch when possible
- affected>= 1e9ea7e04472d4e5e12e58c881eaacfb3e49b669 and < 34a49b3e94a50f45b62c6e6f574f676a079ba23e
- affected>= 1e9ea7e04472d4e5e12e58c881eaacfb3e49b669 and < 14bc34fe948523dc2b0174691f9af9e74eb4f3fd
- 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.