CVE-2026-89611
Last modified
CVE-2026-89611 is a critical-severity vulnerability rated 9.8/10 on the CVSS scale. In the Linux kernel, the following vulnerability has been resolved: ntfs: validate non-resident attribute offsets ntfs_attr_update_meta() shifts the attribute name when converting between non-sparse and sparse attributes. Converting to sparse also adds the compressed_size field before the name and mapping pairs, requiring eight additional bytes in the attribute record. However, the validator does not check that name_offset is within safe boundaries for these operations or that the additional space is available. A malicious MFT record could set name_offset such that: 1. EPSS estimates a 0.15% chance of exploitation in the next 30 days.
Description
In the Linux kernel, the following vulnerability has been resolved: ntfs: validate non-resident attribute offsets ntfs_attr_update_meta() shifts the attribute name when converting between non-sparse and sparse attributes. Converting to sparse also adds the compressed_size field before the name and mapping pairs, requiring eight additional bytes in the attribute record. However, the validator does not check that name_offset is within safe boundaries for these operations or that the additional space is available. A malicious MFT record could set name_offset such that: 1. The name is positioned at the very end of a non-sparse attribute. Converting to sparse would shift the name forward by 8 bytes, writing beyond the attribute boundary. 2. The name overlaps with the mapping pairs, causing corruption during conversion. Add validation to ensure: - For named attributes, name_offset is within valid bounds - Name does not extend beyond the attribute or overlap with mapping pairs - For non-sparse, non-compressed attributes, eight bytes are available after mapping_pairs_offset for the compressed_size field The space check also covers unnamed attributes, for which name_offset = 0 is valid and no name range needs to be checked.
Metrics
Affected Software
Source: CNA advisory (CVE.org). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, < cd7b3dc7557faadeea626034e3bac68a449851ef; >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, < a83e82b0ec3ae523028e24813f23f18b43e8fc1c; < 7.2.4 |
| Linux | Linux | All versions |
References
Timeline
- Published
- Last Modified
- Status
- Received
Frequently Asked Questions
What is CVE-2026-89611?
How severe is CVE-2026-89611?
How do I fix CVE-2026-89611?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-89606In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-89607In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-89608In the Linux kernel, the following vulnerability has been re…7.1
- CVE-2026-89609In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-8961Spoofing issue in the Form Autofill component. This vulnerab…6.5
- CVE-2026-89610In the Linux kernel, the following vulnerability has been re…9.8
- CVE-2026-89612In the Linux kernel, the following vulnerability has been re…9.8
- CVE-2026-89613In the Linux kernel, the following vulnerability has been re…9.8
- CVE-2026-89614In the Linux kernel, the following vulnerability has been re…9.8
- CVE-2026-89615In the Linux kernel, the following vulnerability has been re…8.4
- CVE-2026-89616In the Linux kernel, the following vulnerability has been re…7.5
- CVE-2026-89617In the Linux kernel, the following vulnerability has been re…7.8
Are you affected by CVE-2026-89611?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
