CVE-2026-72477
Linux ntfs3 rename bug can leave inodes inconsistent, risking data corruption and DoS.
Is CVE-2026-72477 being exploited?
Not confirmed. CVE-2026-72477 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-72477?
CVE-2026-72477 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-72477?
Yes. A fix has been recorded for CVE-2026-72477. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-72477 affect?
CVE-2026-72477 affects Linux kernel ntfs3 filesystem driver, Distributions using kernels with ntfs3 (mainline and backports). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-72477?
Apply updated Linux kernel with ntfs3 fix; check/remount and run fsck on NTFS volumes.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Local user or attacker with write/mount access can trigger inode inconsistency on NTFS, causing kernel WARN, data corruption or denial of service.
Patch when possible
- affected>= 519b078998ce6e729f98dccf35505b4756985d11 and < ff825bf0521f6da2f30878cbad18ab7b341bc31b
- affected>= 519b078998ce6e729f98dccf35505b4756985d11 and < e8ed78f40eecd0176fda71d673f6957c98e7ffbe
- affected6.17
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.