CVE-2026-80673: ntfs: bound the look-ahead attribute-list entry in ntfs_external_attr_find()
In the Linux kernel, the following vulnerability has been resolved:
ntfs: bound the look-ahead attribute-list entry in ntfs_external_attr_find()
When resolving an attribute lookup with a non-zero @lowest_vcn,
ntfs_external_attr_find() peeks at the next $ATTRIBUTE_LIST entry to
decide whether to keep searching, but bounds that not-yet-validated
entry only with "(u8 *)next_al_entry + 6 < al_end" (which proves just
bytes 0..6 are in range) and "(u8 *)next_al_entry + length <= al_end"
with an attacker-controlled, non-8-aligned length. It then reads
next_al_entry->lowest_vcn (an __le64 at offset 8) and the name at
next_al_entry->name_offset, both of which can lie past al_end -- the
exact end of the kvmalloc'd attribute-list buffer (allocated at the
on-disk attr_list_size, no rounding). A crafted on-disk $ATTRIBUTE_LIST
whose last entry sits a few bytes before al_end therefore yields a slab
out-of-bounds read when the inode is read.
Validate the look-ahead entry with ntfs_attr_list_entry_is_valid() (added
in patch 1/3) before dereferencing lowest_vcn and the name, so the same
fixed-header, length and name bounds the main attribute-list walk uses now
guard this read too.
Security readout for executives and security teams
Plain-English summary
A malformed NTFS filesystem can make the Linux kernel read beyond an allocated memory buffer while examining file metadata. The record rates this critical, but the supplied technical evidence establishes an out-of-bounds read, not a demonstrated path to complete system compromise.
Executive priority
Prioritize exposed systems that automatically mount or inspect untrusted NTFS content. Patch promptly, while recognizing that the critical score overstates what the supplied technical narrative alone proves. Systems without NTFS exposure should be assessed rather than assumed vulnerable.
Technical view
ntfs_external_attr_find() insufficiently validated a look-ahead $ATTRIBUTE_LIST entry before reading lowest_vcn and name data. A crafted final entry near the attribute-list buffer boundary can trigger a slab out-of-bounds read when the inode is read. The referenced correction validates that entry with ntfs_attr_list_entry_is_valid() before dereferencing it.
Likely exposure
The bundle identifies Linux versions spanning 7.1 through 7.2 as affected, although its version data is ambiguous. Practical exposure appears concentrated where vulnerable kernels read attacker-controlled NTFS filesystems, disk images, or media. Confirm exact affected and fixed versions with kernel or distribution guidance.
Exploitation context
No active exploitation is established: the bundle states KEV is false and provides no exploitation report. An attacker must supply a specially crafted on-disk NTFS $ATTRIBUTE_LIST and cause the vulnerable kernel to read the associated inode. Remote reachability is not demonstrated despite the supplied CVSS network vector.
Researcher notes
The demonstrated primitive is a slab out-of-bounds read caused by inadequate fixed-header, length, alignment, and name bounds validation. The record assigns CVSS 9.8 with high confidentiality, integrity, and availability impact, but the supplied sources do not document code execution, memory corruption through writing, or an exploitation chain.
Mitigation direction
Install a vendor-supported kernel containing the referenced stable correction.
Check distribution guidance for precise affected and fixed package versions.
Restrict processing or mounting of untrusted NTFS media and images until updated.
Reduce attacker-controlled access to workflows that inspect NTFS filesystems.
Validation and detection
Inventory kernel versions and systems with NTFS support or NTFS-processing workflows.
Verify the installed kernel includes the referenced validation correction.
Confirm untrusted NTFS media and images are restricted before remediation.
Review distribution advisories when available to resolve the ambiguous version boundaries.
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-80673 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.