CVE-2026-45935

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.

Weakness

The product reads data past the end, or before the beginning, of the intended buffer.

Affected Software

Potential Mitigations

• Assume all input is malicious. Use an “accept known good” input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.
• When performing input validation, consider all potentially relevant properties, including length, type of input, the full range of acceptable values, missing or extra inputs, syntax, consistency across related fields, and conformance to business rules. As an example of business rule logic, “boat” may be syntactically valid because it only contains alphanumeric characters, but it is not valid if the input is only expected to contain colors such as “red” or “blue.”
• Do not rely exclusively on looking for malicious or malformed inputs. This is likely to miss at least one undesirable input, especially if the code’s environment changes. This can give attackers enough room to bypass the intended validation. However, denylists can be useful for detecting potential attacks or determining which inputs are so malformed that they should be rejected outright.
• To reduce the likelihood of introducing an out-of-bounds read, ensure that you validate and ensure correct calculations for any length argument, buffer size calculation, or offset. Be especially careful of relying on a sentinel (i.e. special character such as NUL) in untrusted inputs.

Related Attack Patterns

• https://cwe.mitre.org/data/definitions/540.html

References

• https://git.kernel.org/stable/c/36c03f7f177b34d51f1cf1d2304b1074607bf4b0
• https://git.kernel.org/stable/c/78942172d5bff4d4afed8674abc09cc560ce44a0
• https://git.kernel.org/stable/c/a584b9d1059b29e97e17c919274e9adfb846f2a0
• https://git.kernel.org/stable/c/b271c9cb85927210b1b799e55ee7f702d12b4336
• https://git.kernel.org/stable/c/b2bc7c44ed1779fc9eaab9a186db0f0d01439622
• https://git.kernel.org/stable/c/c065541b71b79874c83d418a9acd18ad5826339b
• https://git.kernel.org/stable/c/f3b437a4c3e022a1449658ae9f3dd34859894513