fs/ntfs3: Fix slab-out-of-bounds read in DeleteIndexEntryRoot
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ b46acd6a6a627d876898e1c84d3f84902264b445 · < f3b437a4c3e022a1449658ae9f3dd34859894513| No fix yet |
| Linux Linux |
|
|
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.
From the CVE record · Linux
The Linux kernel’s ntfs3 filesystem does not adequately check an entry size read from a log record in DeleteIndexEntryRoot. A maliciously large size can cause an out-of-bounds memory operation and heap buffer overflow. The input does not specify whether exploitation requires local access, authentication, or user interaction.
Engineers running the Linux kernel with ntfs3 should check their systems; affected versions are not specified.