Answer in brief
CVE-2026-72196 records a High severity (CVSS 8.4) vulnerability in fs/ntfs3: bound copy_lcns dp->page_lcns[] index in analysis pass. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 8.4. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=b46acd6a6a627d876898e1c84d3f84902264b445 <9b3d8cc9d54fcded4de51b2b1026ae7182512077 || >=b46acd6a6a627d876898e1c84d3f84902264b445 <9b7c28d8c61bdb041936222a09a708531a1c2921 || >=b46acd6a6a627d876898e1c84d3f84902264b445 <0f13e823bf86bd1800168ea0bb5bca8b8500a81c || >=b46acd6a6a627d876898e1c84d3f84902264b445 <d240cd98f5f7b65c90f6b2b6abe3232ccdc405ab || >=b46acd6a6a627d876898e1c84d3f84902264b445 <49c86dae0c0ccb8d98ddcdc46987259389c816dd || >=b46acd6a6a627d876898e1c84d3f84902264b445 <5e7b598660cfa8e5af172cf4c65cffc126333307 | 9b3d8cc9d54fcded4de51b2b1026ae7182512077, 9b7c28d8c61bdb041936222a09a708531a1c2921, 0f13e823bf86bd1800168ea0bb5bca8b8500a81c, d240cd98f5f7b65c90f6b2b6abe3232ccdc405ab, 49c86dae0c0ccb8d98ddcdc46987259389c816dd, 5e7b598660cfa8e5af172cf4c65cffc126333307 |
| Linux/Linuxgeneric | 5.15 | Not reported |
Published upstream
Aug 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 17, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 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", <[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]
Quoted source text, attributed separately from HOL analysis.