# CVE-2026-72204: ntfs: centalize $INDEX_ROOT header validation

> Insufficient validation of NTFS index root headers in the Linux kernel allows attackers to trigger memory corruption, potentially leading to code execution or system crashes.

- **Severity:** High 8.4 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 15 Aug 2026
- **Updated:** 18 Aug 2026
- **Also known as:** DEBIAN-CVE-2026-72204, GHSA-2vp7-pvhw-wqqx, UBUNTU-CVE-2026-72204

## What is CVE-2026-72204?

CVE-2026-72204 is a high-severity memory corruption vulnerability in Linux, published on 15 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

In the Linux kernel, the following vulnerability has been resolved:

ntfs: centalize $INDEX_ROOT header validation

Add a dedicated helper to perform stricter validation of $INDEX_ROOT and
use it for both directory inodes and named index inodes. This keeps the
root size and header geometry checks consistent across both read paths.

## Which versions are affected by CVE-2026-72204?


## How do I fix CVE-2026-72204?

Apply the vendor's patch.

## Is CVE-2026-72204 being exploited?

There is no known exploitation of CVE-2026-72204 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-72204 and fix it if it is affected.

What it is: CVE-2026-72204 is a high-severity memory corruption vulnerability in Linux, published on 15 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-72204 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-72204/ (Markdown: https://insights.sbomify.com/CVE-2026-72204/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-72204
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-72204
- OSV: https://osv.dev/vulnerability/CVE-2026-72204

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-72204/
Summaries are generated and may contain mistakes; the official description above is the record.