CVE-2026-72196
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.
| Package | Ecosystem | Fixed in |
|---|---|---|
| kernel | Amazon Linux | 1:6.1.180-225.360.amzn2023 |
Risk scores
Affected products
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | b46acd6a6a627d876898e1c84d3f84902264b445, b46acd6a6a627d876898e1c84d3f84902264b445, b46acd6a6a627d876898e1c84d3f84902264b445 |
| Linux | Linux | 5.15, 0, 6.1.178 |
| amazon:2023 | kernel | 0 |
| linux | linux_kernel | 5.15, 5.15, 5.15 |
| Linux | Linux | *, 7.2, 7.1.5 |
| amazon:2023 | python3-perf6.12 | 0 |
| amazon:2023 | kernel6.12-modules-extra-common | 0 |
| amazon:2023 | kernel6.18-headers | 0 |
| amazon:2023 | kernel6.18-modules-extra | 0 |
| amazon:2023 | kernel6.18-modules-extra-common | 0 |
| amazon:2023 | kernel-headers | 0 |
| amazon:2023 | kernel6.12-headers | 0 |
| amazon:2023 | kernel-livepatch-6.18.41-94.142 | 0 |
| amazon:2023 | kernel6.12 | 0 |
| amazon:2023 | kernel6.12-tools | 0 |
| amazon:2023 | kernel-livepatch-6.12.100-125.179 | 0 |
| amazon:2023 | python3-perf6.18 | 0 |
| amazon:2023 | perf6.18 | 0 |
| amazon:2023 | kernel6.18-tools | 0 |
| amazon:2023 | kernel6.12-devel | 0 |
…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