CVE-2026-72194fs/ntfs3: add depth limit to indx_find_buffer to prevent stack overflow
- 9.8CriticalCVSS base score
- 0.80%Exploitation in 30 daysEPSS · top 43% 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: fs/ntfs3: add depth limit to indx_find_buffer to prevent stack overflow indx_find_buffer() recursively descends the B+ tree index with no depth limit. A crafted NTFS image with circular index node references causes unbounded recursion, overflowing the kernel stack and panicking the system. This is reachable by mounting a malicious NTFS filesystem (e.g. from a USB drive via desktop automount) and deleting a file whose index entry triggers the rebalancing fallback path in indx_delete_entry(). Add a depth parameter and bail out with -EINVAL when it reaches the fnd->nodes array bound, matching the constraint already enforced by fnd_push() in indx_find(). The related function indx_find() was previously patched for a similar infinite-loop issue (commit 1732053c8a6b), but indx_find_buffer() was missed.
Timeline
ID reserved
By Linux
- 6 days later
· 6 days later
Published
- 2 months later
· 2 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
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| LinuxCNA (assigner) | 3.1 | Critical9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| NVDNVD · Received | 3.1 | Critical9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
- EPSS (exploitation in 30 days)
- 0.80% · top 43% of all CVEs (16 Nov 2026)
- CISA SSVC
- Exploitation: none · Automatable: yes · Technical impact: total
The list uses the assigner's score when there is one, then CISA's, then NVD's: Critical 9.8.
Affected products
- affected 82cae269cfa953032fbb8980a7d554d60fb00b17 – < 99031d4f63c785d2a985b6a4c64c4256f7117052
- affected 82cae269cfa953032fbb8980a7d554d60fb00b17 – < 65357a81f64cb3fbe13b4b937586755e4b3a072f
- affected 82cae269cfa953032fbb8980a7d554d60fb00b17 – < 96fb64f9da86fd2dbd78fbe9d9e41ae27e12ce34
- affected 82cae269cfa953032fbb8980a7d554d60fb00b17 – < 78612f478f9fadcec4f9b3b089970da67ffb47e9
- affected 82cae269cfa953032fbb8980a7d554d60fb00b17 – < 908c9243ba309997b73cbda3e4c563d0fb345ee9
- affected 82cae269cfa953032fbb8980a7d554d60fb00b17 – < fdf50c788e0991e42a187ff75479a0df7fb752f1
- affected 82cae269cfa953032fbb8980a7d554d60fb00b17 – < 1ebd684b8f627f75bc3e03f8b2ad8400fd1f02cd
- 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/99031d4f63c785d2a985b6a4c64c4256f7117052 (opens in a new tab)
- https://git.kernel.org/stable/c/65357a81f64cb3fbe13b4b937586755e4b3a072f (opens in a new tab)
- https://git.kernel.org/stable/c/96fb64f9da86fd2dbd78fbe9d9e41ae27e12ce34 (opens in a new tab)
- https://git.kernel.org/stable/c/78612f478f9fadcec4f9b3b089970da67ffb47e9 (opens in a new tab)
- https://git.kernel.org/stable/c/908c9243ba309997b73cbda3e4c563d0fb345ee9 (opens in a new tab)
- https://git.kernel.org/stable/c/fdf50c788e0991e42a187ff75479a0df7fb752f1 (opens in a new tab)
- https://git.kernel.org/stable/c/1ebd684b8f627f75bc3e03f8b2ad8400fd1f02cd (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-58952 (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-72194)Record last updated .