CVE-2026-72208: ntfs: add bounds check before accessing EA entries
In the Linux kernel, the following vulnerability has been resolved:
ntfs: add bounds check before accessing EA entries
in ntfs_ea_lookup and ntfs_listxattr, this verifies that there is enough
space in the EA entry before accessing the next_entry_offset field of
the EA entry.
Security readout for executives and security teams
Plain-English summary
Linux could read beyond a valid NTFS extended-attribute entry because it did not first confirm enough data remained. The record assigns CVSS 9.8, indicating potentially severe confidentiality, integrity, and availability impact, but the supplied sources do not describe a demonstrated outcome or attack path.
Executive priority
Treat as an urgent validation and patching issue where Linux systems process NTFS data. Prioritize exposed or untrusted-data workflows, but do not assume remote compromise solely from the CVSS vector because the supplied evidence does not document an end-to-end attack path.
Technical view
The flaw affects ntfs_ea_lookup and ntfs_listxattr. Both could access an EA entry's next_entry_offset field without first verifying that the entry contained enough bytes. The referenced stable-kernel commits add the missing bounds check. The supplied evidence does not establish the resulting memory-safety consequence.
Likely exposure
The record identifies Linux 7.1, 7.1.5, and 7.2 as affected, while other version data is ambiguous. Systems processing NTFS extended attributes through the affected functions warrant validation. The bundle does not explain whether ordinary remote services expose this path.
Exploitation context
No CISA KEV listing is reported, and the supplied sources provide no evidence of active exploitation, public proof-of-concept code, or a confirmed attack chain. Although the CVSS vector states network reachability without privileges or interaction, the sources do not explain how network input reaches the NTFS code.
Researcher notes
The source bundle supplies no CWE, crash details, proof of concept, affected distribution mapping, or explicit consequence beyond the missing bounds check. Version information is unusually narrow and partly ambiguous. Confirm reachability and fixed-package status through kernel or distribution guidance before making fleet-wide exposure claims.
Mitigation direction
Identify systems running the specifically listed Linux versions.
Obtain vendor guidance mapping the fix to supported distribution kernels.
Update to a vendor kernel incorporating the referenced stable fix.
Restrict unnecessary NTFS processing until affected systems are updated.
Validation and detection
Record running kernel and distribution package versions across Linux assets.
Compare vendor advisories against both referenced stable-kernel commits.
Confirm patched source checks EA-entry bounds before reading next_entry_offset.
Retest NTFS extended-attribute operations after updating affected systems.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2026-72208 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
3Timeline events
0ADP providers
3Source links
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.