{"cve":"CVE-2026-72211","nvd":{"published":"2026-08-15T06:21:39.803","modified":"2026-08-18T07:16:54.370","status":"Received","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nntfs: grow index root value before reparent header update\n\nntfs_ir_reparent() moves the resident index root entries into an index\nblock and leaves a small root stub containing the child VCN. That root\nstub can be larger than the existing resident value. For example, an\nempty root with value_length 48 has an index area of 32 bytes, while the\nlarge-index root stub needs index_length and allocated_size of 40 bytes.\n\nThe current code publishes the larger index.index_length and\nindex.allocated_size before resizing the resident value. If the resize\nreturns -ENOSPC, the recovery path can call ntfs_inode_add_attrlist(),\nwhich looks attributes up again while the root header says\nallocated_size 40 but the resident value still only provides 32 bytes of\nindex area. Lookup-time $INDEX_ROOT validation then correctly rejects\nthat transient layout as corrupt.\n\nThis reproduces as a generic/013 failure under qemu. In the failing run,\nthe transient root had value_len=48, index_size=32, index_length=40, and\nallocated_size=40, and ntfsprogs-plus ntfsck reported \"Corrupt index\nroot in MFT record 1177\".\n\nWhen the root stub grows, resize the resident value before publishing the\nlarger root header. If the resize fails, the old root remains valid for\nrecovery lookups. Keep the existing header-before-resize ordering for\nshrink or same-size cases so the resident value never temporarily\nexposes an allocated_size beyond its bounds.","cvss_v4":null,"cvss_v3":{"version":"3.1","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","score":9.8},"cwes":[],"references":["https://git.kernel.org/stable/c/0bb508fb3b97e4802ec727fd2af4d608f65dd190","https://git.kernel.org/stable/c/38d444271604afc6381ddb5a181e391915c35fae"],"products":[],"source":"nvd","synced_at":"2026-10-19T22:48:17.459049833+00:00"},"epss":{"cve":"CVE-2026-72211","score":0.00553,"percentile":0.46217,"date":"2026-10-31"},"kev":null,"osv":[],"attribution":["This product uses the NVD API but is not endorsed or certified by the NVD.","EPSS scores: FIRST Exploit Prediction Scoring System, https://www.first.org/epss","Known exploited vulnerabilities: CISA Known Exploited Vulnerabilities Catalog, https://www.cisa.gov/known-exploited-vulnerabilities-catalog","Package advisories: OSV (https://osv.dev), from the GitHub Advisory Database, PyPA, Go, RustSec and other ecosystem databases, under CC-BY 4.0 or CC0","CVE records: the CVE Program's CVE List (https://www.cve.org), under its terms of use (https://www.cve.org/Legal/TermsOfUse). CVE is a registered trademark of The MITRE Corporation; this product is not affiliated with the CVE Program."]}