Skip to content
Systems

CVE-2026-72209

CRITICAL
Critical
EPSS 0.52%Patch availableAug 17, 2026

Linux kernel NTFS parsing flaw allows kernel memory OOB read and crash.

common questions

Is CVE-2026-72209 being exploited?

Not confirmed. CVE-2026-72209 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-72209?

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

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

What does CVE-2026-72209 affect?

CVE-2026-72209 affects Linux kernel (ntfs/ntfs3 driver), Servers, VMs, desktops mounting untrusted NTFS images. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-72209?

Apply kernel updates promptly; avoid mounting untrusted NTFS images; reboot after patch.

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

executive summary
technical analysis
affected
Linux kernel (ntfs/ntfs3 driver)Servers, VMs, desktops mounting untrusted NTFS images
impact

Out-of-bounds read in NTFS kernel driver from crafted NTFS images; can leak kernel memory and crash (DoS); may aid privilege escalation when chained.

action required

Immediate action required

affected versions
Linux Linux
  • affected>= 6ceb4cc81ef3409ff79dcb959771f9110787397a and < e4c36dfac57a7261e9aeb0f3a7f30944a8aefb56
  • affected>= 6ceb4cc81ef3409ff79dcb959771f9110787397a and < d5803e3345dae9c6470bb61869885236276b9a35
  • affected7.1
vendor says fixed in< 7.1, >= 7.1.5 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