Skip to content
Systems

CVE-2026-72192

9.8
Critical
EPSS 0.73%Patch availableAug 17, 2026

Local heap overflow in Linux ntfs3 driver enabling privilege escalation

common questions

Is CVE-2026-72192 being exploited?

Not confirmed. CVE-2026-72192 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.73% probability of exploitation in the next 30 days.

How severe is CVE-2026-72192?

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

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

What does CVE-2026-72192 affect?

CVE-2026-72192 affects Linux kernel ntfs3 driver, Linux systems mounting attacker-crafted NTFS images. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-72192?

Apply available kernel/ntfs3 updates or avoid mounting untrusted NTFS images; unload/disable ntfs3 if necessary.

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

executive summary
technical analysis
affected
Linux kernel ntfs3 driverLinux systems mounting attacker-crafted NTFS images
impact

Bounded adjacent-heap write via crafted NTFS image allowing local privilege escalation to root on vulnerable Linux kernels.

action required

Immediate action required

affected versions
Linux Linux
  • affected>= 82cae269cfa953032fbb8980a7d554d60fb00b17 and < 0af83b8155cc848e9f5d2c36e20a70d024214649
  • affected>= 82cae269cfa953032fbb8980a7d554d60fb00b17 and < cb3161deebcaf8d36d3115abf452c633f2180fc1
  • affected>= 82cae269cfa953032fbb8980a7d554d60fb00b17 and < 53c5f3b2da3774b41534728aba295c098c9efa19
  • affected>= 82cae269cfa953032fbb8980a7d554d60fb00b17 and < 194b00c99ba971fa7cf6acd747a36032c6de54eb
  • affected>= 82cae269cfa953032fbb8980a7d554d60fb00b17 and < aaa1f956c0fc41089a4a534da7df91552a08a47c
  • affected>= 82cae269cfa953032fbb8980a7d554d60fb00b17 and < d240f5f9d036b8180224954d9873f172b6be4dd8
  • affected>= 82cae269cfa953032fbb8980a7d554d60fb00b17 and < 9b6926ac9c970ae0b2c2fe6289b16e9aa10b6a67
  • affected5.15
vendor says fixed in< 5.15, >= 5.15.212 and <= 5.15.*, >= 6.1.178 and <= 6.1.*, >= 6.6.145 and <= 6.6.*, >= 6.12.97 and <= 6.12.*, >= 6.18.40 and <= 6.18.*, >= 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