CVE-2026-72193ntfs3: cap RESTART_TABLE free-chain walker at rt->used
- —Not scoredno CVSS score yet
- 0.21%Exploitation in 30 daysEPSS · top 88% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
Description
In the Linux kernel, the following vulnerability has been resolved: ntfs3: cap RESTART_TABLE free-chain walker at rt->used A crafted NTFS3 disk image triggers an in-kernel infinite loop at mount time, hanging the mounting thread and firing the soft-lockup watchdog within ~22s on multi-CPU hosts (panic with kernel.softlockup_panic=1). The bug is reachable from desktop USB auto-mount on distributions where udisks2 routes the NTFS signature to the in-tree ntfs3 driver (Arch family and an increasing fraction of Fedora / openSUSE / RHEL deployments); CAP_SYS_ADMIN-class manual mount elsewhere. check_rstbl()'s second walker iterates the free-entry singly-linked list headed by rt->first_free with no upper bound on iteration count: for (off = ff; off;) { if (off == RESTART_ENTRY_ALLOCATED) return false; off = le32_to_cpu(*(__le32 *)Add2Ptr(rt, off)); if (off > ts - sizeof(__le32)) return false; } The existing guards cover three exits: end-of-list (off == 0), the in-use marker (off == RESTART_ENTRY_ALLOCATED), and out-of-bounds (off > ts - sizeof(__le32)). None of the three prevents an in-bounds cycle. A crafted on-disk RESTART_TABLE whose free chain contains a self-loop or A->B->A cycle whose offsets satisfy: - in range [sizeof(struct RESTART_TABLE), ts - sizeof(__le32)] - (off - sizeof(struct RESTART_TABLE)) % rsize == 0 passes all existing guards and spins the mount-time thread forever. Reproduced in UML by hand-forging a 2 MB NTFS3 image whose journal RESTART_TABLE first_free = 0x18 and whose entry at offset 0x18 stores 0x18 as its next pointer; mount of the forged image with the in-tree ntfs3 driver never returns. Bound the walker by rt->used. Each entry on a legitimate free chain is unique, and the total slot count is ne = le16_to_cpu (rt->used). A traversal that visits more than ne slots is by construction malformed; reject it as a corrupt RESTART_TABLE. After this patch, mount of the forged image returns with -EINVAL and a log_replay failure message, and mkntfs-produced legitimate images mount cleanly (verified in the same UML harness).
Timeline
ID reserved
By Linux
- 6 days later
· 6 days later
Published
- 3 months later
· 3 months later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.
- EPSS (exploitation in 30 days)
- 0.21% · top 88% of all CVEs (16 Nov 2026)
- CISA SSVC
- Exploitation: none · Automatable: no · Technical impact: partial
The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.
Affected products
- affected b46acd6a6a627d876898e1c84d3f84902264b445 – < 8128bec895075253c779d67afdc90ae513265fca
- affected b46acd6a6a627d876898e1c84d3f84902264b445 – < 7972df425687daa70d971fe6ed415e78683133dd
- affected b46acd6a6a627d876898e1c84d3f84902264b445 – < 7ac4c86915c24c208a0f0611b71d9676686fe756
- affected b46acd6a6a627d876898e1c84d3f84902264b445 – < 29b86dbe88cbbef53bb9aaec2e279359f8c450f8
- affected b46acd6a6a627d876898e1c84d3f84902264b445 – < 0fad25687d4d3fa1fdd313d31b9cb5817c425029
- affected b46acd6a6a627d876898e1c84d3f84902264b445 – < d313416280d41bea272f02a6034dfa88008692a0
- affected b46acd6a6a627d876898e1c84d3f84902264b445 – < 9611f644302c07d21bc8af97e3e06a3d30064253
- affected 5.15
- unaffected < 5.15
- unaffected 5.15.212 – ≤ 5.15.*
- unaffected 6.1.178 – ≤ 6.1.*
- unaffected 6.6.145 – ≤ 6.6.*
- unaffected 6.12.97 – ≤ 6.12.*
- unaffected 6.18.40 – ≤ 6.18.*
- unaffected 7.1.5 – ≤ 7.1.*
- unaffected 7.2 – ≤ *
References
References7
- https://git.kernel.org/stable/c/8128bec895075253c779d67afdc90ae513265fca (opens in a new tab)
- https://git.kernel.org/stable/c/7972df425687daa70d971fe6ed415e78683133dd (opens in a new tab)
- https://git.kernel.org/stable/c/7ac4c86915c24c208a0f0611b71d9676686fe756 (opens in a new tab)
- https://git.kernel.org/stable/c/29b86dbe88cbbef53bb9aaec2e279359f8c450f8 (opens in a new tab)
- https://git.kernel.org/stable/c/0fad25687d4d3fa1fdd313d31b9cb5817c425029 (opens in a new tab)
- https://git.kernel.org/stable/c/d313416280d41bea272f02a6034dfa88008692a0 (opens in a new tab)
- https://git.kernel.org/stable/c/9611f644302c07d21bc8af97e3e06a3d30064253 (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-58951 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-72193)Record last updated .