fs/ntfs3: add depth limit to indx_find_buffer to prevent stack overflow
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 82cae269cfa953032fbb8980a7d554d60fb00b17 · < fdf50c788e0991e42a187ff75479a0df7fb752f1| No fix yet |
| Linux Linux |
|
|
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.
From the CVE record · Linux
The Linux kernel’s ntfs3 filesystem has no recursion depth limit in indx_find_buffer(). A crafted NTFS image with circular index references can overflow the kernel stack and panic the system when the filesystem is mounted and a file deletion triggers the affected index-rebalancing path. The image could be supplied on a USB drive and mounted by desktop automount.
Anyone running a Linux kernel that uses ntfs3 to mount NTFS filesystems should check their kernel; affected versions were not specified.