fs/ntfs3: validate lcns_follow in log_replay conversion
- 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
- Fix
- Fixed in 5.15.212, 6.1.178, 6.6.145, 6.12.97, 6.18.40, and 1 more
- 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
- Exploitation: none
- Automatable: no
- Technical impact: total
Summary
In the Linux kernel, the following vulnerability has been resolved: fs/ntfs3: validate lcns_follow in log_replay conversion log_replay() converts DIR_PAGE_ENTRY_32 records into DIR_PAGE_ENTRY records when replaying version 0 restart tables. During this conversion, the memmove() length is derived directly from the on-disk lcns_follow field: memmove(&dp->vcn, &dp0->vcn_low, 2 * sizeof(u64) + le32_to_cpu(dp->lcns_follow) * sizeof(u64)); check_rstbl() validates restart table structure, but does not constrain per-entry lcns_follow values relative to the entry size. A malformed filesystem image can provide an oversized lcns_follow value, causing the conversion memmove() to access memory beyond the bounds of the allocated restart table buffer. The same field is later used to bound iteration over page_lcns[], so validating lcns_follow during conversion also prevents downstream out-of-bounds access from the same malformed metadata. Compute the maximum valid lcns_follow from the already-validated restart table entry size and reject entries that exceed this bound. Reuse the existing t16/t32 scratch variables already declared in log_replay() to avoid introducing new declarations. [almaz.alexandrovich@paragon-software.com: fixed the conflicts]
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- Linux Linux
From b46acd6a6a627d876898e1c84d3f84902264b445 · fixed in ca343a99806b4fc8e27c48f08be3445c5fcd1445; From b46acd6a6a627d876898e1c84d3f84902264b445 · fixed in ddfc8683e1a627dbf1b83bacf8961443dd654258; From b46acd6a6a627d876898e1c84d3f84902264b445 · fixed in 57c071e2c4f30b9c6f5aacb6679aab1269fbae99; From b46acd6a6a627d876898e1c84d3f84902264b445 · fixed in 159f694d682e4215b3822ae31ed3a4631628fe55; From b46acd6a6a627d876898e1c84d3f84902264b445 · fixed in 7adb38279812c9c06b0e3fa7382f4d7887f3fa2d; From b46acd6a6a627d876898e1c84d3f84902264b445 · fixed in 32b9f8733feb241627fa5f564b1a99b5cae974c5; From b46acd6a6a627d876898e1c84d3f84902264b445 · fixed in 6a4c53a2e26a865565bd6a460961e8d6fcb32329
- Linux Linux
5.15
- KernelLinux
From 5.15.0 · fixed in 5.15.212; From 5.16.0 · fixed in 6.1.178; From 6.2.0 · fixed in 6.6.145; From 6.7.0 · fixed in 6.12.97; From 6.13.0 · fixed in 6.18.40; From 6.19.0 · fixed in 7.1.5
References 7
git.kernel.org
- stable/c/ca343a99806b4fc8e27c48f08be3445c5fcd1445
- stable/c/ddfc8683e1a627dbf1b83bacf8961443dd654258
- stable/c/57c071e2c4f30b9c6f5aacb6679aab1269fbae99
- stable/c/159f694d682e4215b3822ae31ed3a4631628fe55
- stable/c/7adb38279812c9c06b0e3fa7382f4d7887f3fa2d
- stable/c/32b9f8733feb241627fa5f564b1a99b5cae974c5
- stable/c/6a4c53a2e26a865565bd6a460961e8d6fcb32329