# CVE-2026-98315: ntfs: protect runlist updates with the runlist lock

> A race condition in the Linux kernel NTFS driver allows concurrent runlist updates to cause memory corruption or data loss.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 6 Oct 2026
- **Updated:** 19 Oct 2026
- **Also known as:** DEBIAN-CVE-2026-98315, GHSA-32pv-963j-mqgr, UBUNTU-CVE-2026-98315

## What is CVE-2026-98315?

CVE-2026-98315 is a high-severity vulnerability in Linux, published on 6 Oct 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: protect runlist updates with the runlist lock

ntfs_non_resident_attr_shrink() calls runlist helpers that require the
runlist write lock, but did not hold it while freeing clusters and
truncating the runlist. Serialize those operations and the resident
conversion with the runlist lock.

ntfs_attr_map_cluster() can merge a newly allocated run before updating
mapping pairs. If the update fails, free the clusters and restore both
the in-memory runlist and on-disk mapping pairs from a saved runlist.
Mark the volume in error if either rollback step fails.

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


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

Apply the vendor's patch.

## Is CVE-2026-98315 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-98315 is a high-severity vulnerability in Linux, published on 6 Oct 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-98315 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-98315/ (Markdown: https://insights.sbomify.com/CVE-2026-98315/index.md)
```

## Sources

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

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