# CVE-2026-99102: ntfs: take invalidate_lock in ntfs_setattr_size()


- **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-99102, GHSA-pchj-j532-7cm6, UBUNTU-CVE-2026-99102

## What is CVE-2026-99102?

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

### Official description

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

ntfs: take invalidate_lock in ntfs_setattr_size()

ntfs_setattr_size() updates i_size and resizes the on-disk attribute
without holding mapping->invalidate_lock.  Page faults take the lock
shared, so a fault racing the resize can resolve a VCN against the
transient runlist state of ntfs_non_resident_attr_expand() and fail
with a spurious SIGBUS, and can interleave with the size-change
epilogue (truncate_pagecache(), i_size_write(),
pagecache_isize_extended()).

Take invalidate_lock exclusively around the whole resize after
inode_dio_wait(), matching the fallocate path and other filesystems
such as xfs, which wraps truncate in its mmaplock (= invalidate_lock).

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


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

Upgrade to a fixed version.

## Is CVE-2026-99102 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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