# CVE-2026-99107: ntfs: fix incorrect MFT record pointer passed to ntfs_attr_record_resize


- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 28 Oct 2026
- **Updated:** 28 Oct 2026
- **Also known as:** DEBIAN-CVE-2026-99107, GHSA-j5gh-3v4f-98gj, UBUNTU-CVE-2026-99107

## What is CVE-2026-99107?

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

### Official description

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

ntfs: fix incorrect MFT record pointer passed to ntfs_attr_record_resize

ntfs_new_attr_flags() passes the wrong MFT record to ntfs_attr_record_resize().
When the attribute is in an extent record, ctx->mrec points to the extent
but the function receives the base record pointer m, causing incorrect
size calculations in memmove.

Fix by passing ctx->mrec (the actual MFT record containing the attribute)
instead of m (the base MFT record) to ntfs_attr_record_resize().

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


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

Upgrade to a fixed version.

## Is CVE-2026-99107 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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