CVE-2026-72211
Last modified
CVE-2026-72211 is a critical-severity vulnerability rated 9.8/10 on the CVSS scale. In the Linux kernel, the following vulnerability has been resolved: ntfs: grow index root value before reparent header update ntfs_ir_reparent() moves the resident index root entries into an index block and leaves a small root stub containing the child VCN. That root stub can be larger than the existing resident value. EPSS estimates a 0.52% chance of exploitation in the next 30 days.
Description
In the Linux kernel, the following vulnerability has been resolved: ntfs: grow index root value before reparent header update ntfs_ir_reparent() moves the resident index root entries into an index block and leaves a small root stub containing the child VCN. That root stub can be larger than the existing resident value. For example, an empty root with value_length 48 has an index area of 32 bytes, while the large-index root stub needs index_length and allocated_size of 40 bytes. The current code publishes the larger index.index_length and index.allocated_size before resizing the resident value. If the resize returns -ENOSPC, the recovery path can call ntfs_inode_add_attrlist(), which looks attributes up again while the root header says allocated_size 40 but the resident value still only provides 32 bytes of index area. Lookup-time $INDEX_ROOT validation then correctly rejects that transient layout as corrupt. This reproduces as a generic/013 failure under qemu. In the failing run, the transient root had value_len=48, index_size=32, index_length=40, and allocated_size=40, and ntfsprogs-plus ntfsck reported "Corrupt index root in MFT record 1177". When the root stub grows, resize the resident value before publishing the larger root header. If the resize fails, the old root remains valid for recovery lookups. Keep the existing header-before-resize ordering for shrink or same-size cases so the resident value never temporarily exposes an allocated_size beyond its bounds.
Metrics
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Affected Software
Source: CNA advisory (CVE.org). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | >= 0a8ac0c1fa0b99a5b29002bc7f232ed7eafddef0, < 38d444271604afc6381ddb5a181e391915c35fae; >= 0a8ac0c1fa0b99a5b29002bc7f232ed7eafddef0, < 0bb508fb3b97e4802ec727fd2af4d608f65dd190 |
| Linux | Linux | 7.1 |
References
Timeline
- Published
- Last Modified
- Status
- Received
Frequently Asked Questions
What is CVE-2026-72211?
How severe is CVE-2026-72211?
How do I fix CVE-2026-72211?
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-72206In the Linux kernel, the following vulnerability has been re…9.8
- CVE-2026-72207In the Linux kernel, the following vulnerability has been re…9.8
- CVE-2026-72208In the Linux kernel, the following vulnerability has been re…9.8
- CVE-2026-72209In the Linux kernel, the following vulnerability has been re…9.8
- CVE-2026-7221A vulnerability was found in TencentCloudBase CloudBase-MCP …7.3
- CVE-2026-72210In the Linux kernel, the following vulnerability has been re…9.8
- CVE-2026-72212In the Linux kernel, the following vulnerability has been re…
- CVE-2026-72213In the Linux kernel, the following vulnerability has been re…7.1
- CVE-2026-72214In the Linux kernel, the following vulnerability has been re…
- CVE-2026-72215In the Linux kernel, the following vulnerability has been re…
- CVE-2026-72216In the Linux kernel, the following vulnerability has been re…
- CVE-2026-72217In the Linux kernel, the following vulnerability has been re…9.8
Are you affected by CVE-2026-72211?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
