ntfs3: add buffer boundary checks to run_unpack()
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 82cae269cfa953032fbb8980a7d554d60fb00b17 · < 41aadf5cb482793a24e05aa136224e179a778586| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
ntfs3: add buffer boundary checks to run_unpack()
run_unpack() checks `run_buf < run_last` at the top of the while loop but then reads size_size and offset_size bytes via run_unpack_s64() without verifying they fit within the remaining buffer. A crafted NTFS image with truncated run data in an MFT attribute triggers an OOB heap read of up to 15 bytes when the filesystem is mounted.
Add boundary checks before each run_unpack_s64() call to ensure the declared field size does not exceed the remaining buffer.
Found by fuzzing with a source-patched harness (LibAFL + QEMU).
From the CVE record · Linux
The Linux kernel's ntfs3 run_unpack() can read beyond a heap buffer when an MFT attribute contains truncated run data. A crafted NTFS image can trigger the read when the filesystem is mounted; the input does not specify authentication requirements or who must mount it.
Engineers running the Linux kernel with ntfs3 should check their systems; affected versions are not specified.