CVE-2026-53027fs/ntfs3: fix missing run load for vcn0 in attr_data_get_block_locked()
- 5.5MediumCVSS base score
- 0.12%Exploitation in 30 daysEPSS · top 98% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
Description
In the Linux kernel, the following vulnerability has been resolved: fs/ntfs3: fix missing run load for vcn0 in attr_data_get_block_locked() When a compressed or sparse attribute has its clusters frame-aligned, vcn is rounded down to the frame start using cmask, which can result in vcn != vcn0. In this case, vcn and vcn0 may reside in different attribute segments. The code already handles the case where vcn is in a different segment by loading its runs before allocation. However, it fails to load runs for vcn0 when vcn0 resides in a different segment than vcn. This causes run_lookup_entry() to return SPARSE_LCN for vcn0 since its segment was never loaded into the in-memory run list, triggering the WARN_ON(1). Fix this by adding a missing check for vcn0 after the existing vcn segment check. If vcn0 falls outside the current segment range [svcn, evcn1), find and load the attribute segment containing vcn0 before performing the run lookup. The following scenario triggers the bug: attr_data_get_block_locked() vcn = vcn0 & cmask <- vcn != vcn0 after frame alignment load runs for vcn segment <- vcn0 segment not loaded! attr_allocate_clusters() <- allocation succeeds run_lookup_entry(vcn0) <- vcn0 not in run -> SPARSE_LCN WARN_ON(1) <- bug fires here!
Timeline
ID reserved
By Linux
- 15 days later
· 15 days later
Published
- 4 months later
· 4 months later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| NVDNVD · Modified | 3.1 | Medium5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
- EPSS (exploitation in 30 days)
- 0.12% · top 98% of all CVEs (19 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.
Affected products
- affected 406a037d93b769bca248476bd14bbe548dc1ec35 – < 543093f65318d012850e548b241f85381b14d643
- affected c380b52f6c5702cc4bdda5e6d456d6c19a201a0b – < ea59d9dbc5504e29d420ac4aab774cbce39b0e69
- affected c380b52f6c5702cc4bdda5e6d456d6c19a201a0b – < d68a14450783ecc5fddae957ac4e1c546dfcfb73
- affected c380b52f6c5702cc4bdda5e6d456d6c19a201a0b – < 08fad5d5a26cc55c0ecb68ac59ba3be5e31f4147
- affected c380b52f6c5702cc4bdda5e6d456d6c19a201a0b – < 2b4ae1ce613ade8a7e118fba4a5a77cd23e97e54
- affected c380b52f6c5702cc4bdda5e6d456d6c19a201a0b – < d7ea8495fd307b58f8867acd81a1b40075b1d3ba
- affected 6.1.132 – < 6.1.191
- affected 6.2
- unaffected < 6.2
- unaffected 6.1.191 – ≤ 6.1.*
- unaffected 6.6.145 – ≤ 6.6.*
- unaffected 6.12.96 – ≤ 6.12.*
- unaffected 6.18.39 – ≤ 6.18.*
- unaffected 7.0.10 – ≤ 7.0.*
- unaffected 7.1 – ≤ *
References
References6
- https://git.kernel.org/stable/c/543093f65318d012850e548b241f85381b14d643 (opens in a new tab)
- https://git.kernel.org/stable/c/ea59d9dbc5504e29d420ac4aab774cbce39b0e69 (opens in a new tab)
- https://git.kernel.org/stable/c/d68a14450783ecc5fddae957ac4e1c546dfcfb73 (opens in a new tab)
- https://git.kernel.org/stable/c/08fad5d5a26cc55c0ecb68ac59ba3be5e31f4147 (opens in a new tab)
- https://git.kernel.org/stable/c/2b4ae1ce613ade8a7e118fba4a5a77cd23e97e54 (opens in a new tab)
- https://git.kernel.org/stable/c/d7ea8495fd307b58f8867acd81a1b40075b1d3ba (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-38895 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-53027)Record last updated .