fs/ntfs3: bound page_lcns[] index by the log record
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ b46acd6a6a627d876898e1c84d3f84902264b445 · < 1135ebc225996b3ac1a295652b19a0a706737a6c| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
fs/ntfs3: bound page_lcns[] index by the log record
The copy_lcns loop and the redo shorten loop index page_lcns[] at j + i, where i runs up to the log record's lcns_follow. That count is checked only against the record's own length, not the target entry, so check_dp_table() (which validates the entry's lcns_follow) does not cover it: the copy_lcns entry may even be freshly allocated after that check, and find_dp() bounds j but not i. A crafted record thus overflows page_lcns[] of an otherwise valid entry.
Add dp_range_ok() and reject, before each loop, any record whose run does not fit the entry. These are the only two page_lcns[] accesses indexed by the record rather than the entry, so together with the entry validation every access is now bounded.
[almaz.alexandrovich@paragon-software.com: original patch contained changes to the problem already handled, applied partly]
From the CVE record · Linux
The Linux kernel's NTFS3 driver can index past the end of a page_lcns[] entry when processing a crafted log record. The record can cause a memory overflow; the input does not specify how an attacker would supply it or whether authentication or user interaction is required.
Engineers running Linux kernels with the NTFS3 driver should check their versions; affected versions are not specified.