CVE-2026-46072
ntfs3: add buffer boundary checks to run_unpack()
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
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).
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
Version range not reported
- Linux Linux
5.15
References 7
git.kernel.org
- stable/c/bbad75336870b51b81979b97613746237fcb02fe
- stable/c/425de2aba0d061b3e715d51a3b1992c112ed5b99
- stable/c/bf7ac4a1d3bfc6e56e54635c3d331a68170d37c9
- stable/c/e64f7dfcaff79e7dfff9121a382dd77f9b462f62
- stable/c/d3012690a7065d9ca86521a525ad11e8af491d45
- stable/c/41aadf5cb482793a24e05aa136224e179a778586
- stable/c/b62567bca47408e6739dee75f02a2113548af875