VDB

CVE-2026-72196

CVE-2026-72196 PUBLISHED CVSS 8.4 HIGH

fs/ntfs3: bound copy_lcns dp->page_lcns[] index in analysis pass

Reported by linux · Published August 15, 2026

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", <20260502154252.164586-1-jhapavitra98@gmail.com>) which addresses the separate version-0 dirty-page-table conversion path's memmove(&dp->vcn, ...) call. The two fixes are complementary; both should land. [almaz.alexandrovich@paragon-software.com: clang-formatted the changes, fixed conflicts]

Fixed versions

Upgrade to a fixed version or later. Language registries are listed first, then Linux distributions, then vendor products.

PackageEcosystemFixed in
kernelAmazon Linux1:6.1.180-225.360.amzn2023

Risk scores

CVSS 3.1
8.4
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Affected products

VendorProductVersions
LinuxLinuxb46acd6a6a627d876898e1c84d3f84902264b445, b46acd6a6a627d876898e1c84d3f84902264b445, b46acd6a6a627d876898e1c84d3f84902264b445
LinuxLinux5.15, 0, 6.1.178
amazon:2023kernel0
linuxlinux_kernel5.15, 5.15, 5.15
LinuxLinux*, 7.2, 7.1.5
amazon:2023python3-perf6.120
amazon:2023kernel6.12-modules-extra-common0
amazon:2023kernel6.18-headers0
amazon:2023kernel6.18-modules-extra0
amazon:2023kernel6.18-modules-extra-common0
amazon:2023kernel-headers0
amazon:2023kernel6.12-headers0
amazon:2023kernel-livepatch-6.18.41-94.1420
amazon:2023kernel6.120
amazon:2023kernel6.12-tools0
amazon:2023kernel-livepatch-6.12.100-125.1790
amazon:2023python3-perf6.180
amazon:2023perf6.180
amazon:2023kernel6.18-tools0
amazon:2023kernel6.12-devel0

…and 18 more

Timeline

  • Aug 15, 2026 Coalition ESS Score
  • Aug 15, 2026 CVE Published
  • Aug 19, 2026 Security Advisory
  • Aug 24, 2026 EPSS Score (13 in total, the first dated here)

Query this with the API

The same record, from the CLI:

vulnetix vdb vuln CVE-2026-72196
vulnetix vdb fixes CVE-2026-72196

Or with curl, using the org id and key from your account page:

curl -s -H "Authorization: ApiKey ${VULNETIX_ORG_ID}:${VULNETIX_API_KEY}" \
  "https://api.vdb.vulnetix.com/v2/vuln/CVE-2026-72196/fixes/registry"

The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart

References

Look up in the Resolve Platform →
$ Lookup Community · 50/day Open Lookup ›