CVE-2025-71266
Description
In the Linux kernel, the following vulnerability has been resolved: fs: ntfs3: check return value of indx_find to avoid infinite loop We found an infinite loop bug in the ntfs3 file system that can lead to a Denial-of-Service (DoS) condition. A malformed dentry in the ntfs3 filesystem can cause the kernel to hang during the lookup operations. By setting the HAS_SUB_NODE flag in an INDEX_ENTRY within a directory's INDEX_ALLOCATION block and manipulating the VCN pointer, an attacker can cause the indx_find() function to repeatedly read the same block, allocating 4 KB of memory each time. The kernel lacks VCN loop detection and depth limits, causing memory exhaustion and an OOM crash. This patch adds a return value check for fnd_push() to prevent a memory exhaustion vulnerability caused by infinite loops. When the index exceeds the size of the fnd->nodes array, fnd_push() returns -EINVAL. The indx_find() function checks this return value and stops processing, preventing further memory allocation.
Predictions
Heuristic predictions, AS-IS, for prioritization only.
Mitigations
No mitigations published for this CVE yet.
The vendor-content worker queues fetches as references arrive (check back in a few minutes). Or — if you've already worked around this in production — publish your fix to the community-verified tier.
✚ Propose a mitigation on Community → Mitigations published via the community go through AI scoring + 2 human reviewers + 7-day silent objection window before landing here withsource_tier=community-verified.
OS impact
Linux kernel Affected 2 releases
| Version | Status | Fixed in |
|---|---|---|
| 5.15 | Affected | — |
| — | Affected | 5.15.202 |
SUSE Affected 1 release
| Version | Status | Fixed in |
|---|---|---|
| — | Affected | — |
Debian Fixed 5 releases
| Version | Status | Fixed in |
|---|---|---|
| trixie | Fixed | 6.12.85-1 |
| sid | Fixed | 6.19.6-1 |
| forky | Fixed | 6.19.6-1 |
| bullseye | Fixed | 0 |
| bookworm | Fixed | 6.1.170-1 |
References
- https://git.kernel.org/stable/c/0ad7a1be44479503dbe5c699759861ef5b8bd70c
- https://git.kernel.org/stable/c/14c3188afbedfd5178bbabb8002487ea14b37b56
- https://git.kernel.org/stable/c/1732053c8a6b360e2d5afb1b34fe9779398b072c
- https://git.kernel.org/stable/c/398e768d1accd1f5645492ab996005d7aa84a5b0
- https://git.kernel.org/stable/c/435d34719db0e130f6f0c621d67ed524cc1a7d10
- https://git.kernel.org/stable/c/68e32694be231c1cdb99b7637a657314e88e1a96
- https://git.kernel.org/stable/c/b0ea441f44ce64fa514a415d4a9e6e2b06e7946c
- https://www.suse.com/security/cve/CVE-2025-71266.html
- https://security-tracker.debian.org/tracker/CVE-2025-71266
CWEs
CWE-835
Community-verified mitigations for this CVE will appear above when contributors publish them.
Verify integrity in audit chain (admin only). AS-IS.