# CVE-2026-72206: ntfs: validate index block header more strictly

> Insufficient validation of NTFS index block headers in the Linux kernel can lead to memory corruption, potentially allowing code execution or system crashes.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/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:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 15 Aug 2026
- **Updated:** 18 Aug 2026
- **Also known as:** DEBIAN-CVE-2026-72206, GHSA-4fpm-842r-3pf4, UBUNTU-CVE-2026-72206

## What is CVE-2026-72206?

CVE-2026-72206 is a critical memory corruption vulnerability in Linux, published on 15 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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

ntfs: validate index block header more strictly

Modify ntfs_index_block_inconsisent() to perform stricter validation of
INDEX_HEADER geometry in INDX blocks, and update
ntfs_lookup_inode_by_name() to use that function to validate INDX
blocks.

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


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

Apply the vendor's patch.

## Is CVE-2026-72206 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-72206 is a critical memory corruption vulnerability in Linux, published on 15 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-72206 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-72206/ (Markdown: https://insights.sbomify.com/CVE-2026-72206/index.md)
```

## Sources

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

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