# CVE-2026-99101: ntfs: move attribute payload before shrinking its record


- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 28 Oct 2026
- **Updated:** 28 Oct 2026
- **Also known as:** AZL-111191, BELL-CVE-2026-99101, DEBIAN-CVE-2026-99101, GHSA-qx38-c9rc-r9x7, UBUNTU-CVE-2026-99101

## What is CVE-2026-99101?

CVE-2026-99101 is a vulnerability in Linux, published on 28 Oct 2026. 

### Official description

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

ntfs: move attribute payload before shrinking its record

ntfs_new_attr_flags() resizes the non-resident attribute record before
moving its name and mapping pairs to their shorter-header offsets when
compression or sparse state is cleared.

Shrinking the record first moves the following attribute over the tail of
the old record. The subsequent memmove() therefore copies bytes from that
following attribute instead of the old mapping pairs. Re-enabling
compression on an empty file persists those bytes as a malformed mapping
pairs array, which ntfsck reports as a missing or invalid run length.

Move the payload before shrinking the record, while retaining the existing
resize-before-move ordering when growing it.

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


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

Upgrade to a fixed version.

## Is CVE-2026-99101 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-99101 is a vulnerability in Linux, published on 28 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-99101 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-99101/ (Markdown: https://insights.sbomify.com/CVE-2026-99101/index.md)
```

## Sources

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

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