Linux kernel ntfs3 is core infrastructure used widely; a kernel memory-corruption bug can enable privilege escalation or widespread DoS, impacting many organizations.
CVE-2026-72196
Out-of-bounds write in Linux ntfs3 during NTFS log replay causing kernel memory corruption.
Is CVE-2026-72196 being exploited?
Not confirmed. CVE-2026-72196 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.18% probability of exploitation in the next 30 days.
How severe is CVE-2026-72196?
CVE-2026-72196 is rated High with a CVSS score of 8.4. 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-72196?
Yes. A fix has been recorded for CVE-2026-72196. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-72196 affect?
CVE-2026-72196 affects Linux kernel (ntfs3 module), Linux distributions using mainline ntfs3, Systems mounting untrusted NTFS images/volumes. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-72196?
Apply kernel update with ntfs3 fix; avoid mounting untrusted NTFS images until patched.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
OOB write in ntfs3 during mount can corrupt kernel memory, enabling local privilege escalation or kernel panic (DoS); occurs with crafted NTFS images.
Patch when possible
- affected>= b46acd6a6a627d876898e1c84d3f84902264b445 and < 9b3d8cc9d54fcded4de51b2b1026ae7182512077
- affected>= b46acd6a6a627d876898e1c84d3f84902264b445 and < 9b7c28d8c61bdb041936222a09a708531a1c2921
- affected>= b46acd6a6a627d876898e1c84d3f84902264b445 and < 0f13e823bf86bd1800168ea0bb5bca8b8500a81c
- affected>= b46acd6a6a627d876898e1c84d3f84902264b445 and < d240cd98f5f7b65c90f6b2b6abe3232ccdc405ab
- affected>= b46acd6a6a627d876898e1c84d3f84902264b445 and < 49c86dae0c0ccb8d98ddcdc46987259389c816dd
- affected>= b46acd6a6a627d876898e1c84d3f84902264b445 and < 5e7b598660cfa8e5af172cf4c65cffc126333307
- affected5.15
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.