fs/ntfs3: Fix slab-out-of-bounds read in DeleteIndexEntryRoot
- 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: fs/ntfs3: Fix slab-out-of-bounds read in DeleteIndexEntryRoot In the 'DeleteIndexEntryRoot' case of the 'do_action' function, the entry size ('esize') is retrieved from the log record without adequate bounds checking. Specifically, the code calculates the end of the entry ('e2') using: e2 = Add2Ptr(e1, esize); It then calculates the size for memmove using 'PtrOffset(e2, ...)', which subtracts the end pointer from the buffer limit. If 'esize' is maliciously large, 'e2' exceeds the used buffer size. This results in a negative offset which, when cast to size_t for memmove, interprets as a massive unsigned integer, leading to a heap buffer overflow. This commit adds a check to ensure that the entry size ('esize') strictly fits within the remaining used space of the index header before performing memory operations.
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/36c03f7f177b34d51f1cf1d2304b1074607bf4b0
- stable/c/b271c9cb85927210b1b799e55ee7f702d12b4336
- stable/c/a584b9d1059b29e97e17c919274e9adfb846f2a0
- stable/c/c065541b71b79874c83d418a9acd18ad5826339b
- stable/c/78942172d5bff4d4afed8674abc09cc560ce44a0
- stable/c/f3b437a4c3e022a1449658ae9f3dd34859894513
- stable/c/b2bc7c44ed1779fc9eaab9a186db0f0d01439622