fs/ntfs3: bound copy_lcns dp->page_lcns[] index in analysis pass
Summary
| CVE | CVE-2026-72196 |
| State | PUBLISHED |
| Assigner | Linux |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2026-08-15 06:21:38 UTC |
| Updated | 2026-08-15 06:21:38 UTC |
| Description | In the Linux kernel, the following vulnerability has been resolved:
fs/ntfs3: bound copy_lcns dp->page_lcns[] index in analysis pass
In log_replay()'s analysis pass, after find_dp() returns a
valid DIR_PAGE_ENTRY for the (target_attr, target_vcn) tuple,
the copy_lcns block walks lrh->lcns_follow further entries:
t16 = le16_to_cpu(lrh->lcns_follow);
for (i = 0; i < t16; i++) {
size_t j = (size_t)(le64_to_cpu(lrh->target_vcn) -
le64_to_cpu(dp->vcn));
dp->page_lcns[j + i] = lrh->page_lcns[i];
}
find_dp() only validates that target_vcn falls within
[dp->vcn, dp->vcn + dp->lcns_follow), i.e., that the FIRST
cluster is covered. The walk through the further entries is
not bounded against dp->lcns_follow. For a malformed LRH
where target_vcn = dp->vcn + dp->lcns_follow - 1 and
lrh->lcns_follow > 1, the i > 0 writes overflow the dp's
allocated page_lcns[] array.
Add the missing j + lrh->lcns_follow <= dp->lcns_follow guard.
Reproduced under UML+KASAN on mainline 8d90b09e6741 as a
slab-out-of-bounds write of size 8 from log_replay+0x68d4 on
the mount path.
This is distinct from Pavitra Jha's 2026-05-02 patch
("fs/ntfs3: validate lcns_follow in log_replay conversion",
<[email protected]>) which
addresses the separate version-0 dirty-page-table conversion
path's memmove(&dp->vcn, ...) call. The two fixes are
complementary; both should land.
[[email protected]: clang-formatted the changes,
fixed conflicts] |
Vendor Declared Affected Products
| Source | Vendor | Product | Version | Platforms |
|---|
| CNA |
Linux |
Linux |
affected b46acd6a6a627d876898e1c84d3f84902264b445 9b3d8cc9d54fcded4de51b2b1026ae7182512077 git |
Not specified |
| CNA |
Linux |
Linux |
affected b46acd6a6a627d876898e1c84d3f84902264b445 9b7c28d8c61bdb041936222a09a708531a1c2921 git |
Not specified |
| CNA |
Linux |
Linux |
affected b46acd6a6a627d876898e1c84d3f84902264b445 0f13e823bf86bd1800168ea0bb5bca8b8500a81c git |
Not specified |
| CNA |
Linux |
Linux |
affected b46acd6a6a627d876898e1c84d3f84902264b445 d240cd98f5f7b65c90f6b2b6abe3232ccdc405ab git |
Not specified |
| CNA |
Linux |
Linux |
affected b46acd6a6a627d876898e1c84d3f84902264b445 49c86dae0c0ccb8d98ddcdc46987259389c816dd git |
Not specified |
| CNA |
Linux |
Linux |
affected b46acd6a6a627d876898e1c84d3f84902264b445 5e7b598660cfa8e5af172cf4c65cffc126333307 git |
Not specified |
| CNA |
Linux |
Linux |
affected 5.15 |
Not specified |
| CNA |
Linux |
Linux |
unaffected 5.15 semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.1.178 6.1.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.6.145 6.6.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.12.97 6.12.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.18.40 6.18.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 7.1.5 7.1.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 7.2-rc1 * original_commit_for_fix |
Not specified |
References
| Reference | Source | Link | Tags |
|---|
| git.kernel.org/stable/c/49c86dae0c0ccb8d98ddcdc46987259389c816dd |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/9b3d8cc9d54fcded4de51b2b1026ae7182512077 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/d240cd98f5f7b65c90f6b2b6abe3232ccdc405ab |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/5e7b598660cfa8e5af172cf4c65cffc126333307 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/9b7c28d8c61bdb041936222a09a708531a1c2921 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/0f13e823bf86bd1800168ea0bb5bca8b8500a81c |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| CVE Program record |
CVE.ORG |
www.cve.org |
canonical |
| NVD vulnerability detail |
NVD |
nvd.nist.gov |
canonical, analysis |
No vendor comments have been submitted for this CVE.
There are currently no legacy QID mappings associated with this CVE.