fs: ntfs3: check return value of indx_find to avoid infinite loop
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 82cae269cfa953032fbb8980a7d554d60fb00b17 · < 0ad7a1be44479503dbe5c699759861ef5b8bd70c| No fix yet |
| Linux Linux |
|
|
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.
From the CVE record · Linux
A malformed directory entry in an ntfs3 filesystem can make the Linux kernel loop during lookup, exhausting memory and causing a hang or out-of-memory crash. An attacker must be able to supply malformed ntfs3 filesystem data; the input does not specify authentication requirements or user interaction.
Anyone running a Linux kernel with ntfs3 should check whether their version includes the fix.