CVE.org (no NVD analysis yet)· CNA Linux

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

Noroxi assessment

Priority: Monitor (action score 0/100)

The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
Probability of exploitation in the next 30 days: 0.15% (FIRST EPSS).
Fixed version: Linux Linux 9cc5761b8f28f9cef72061094eb5e37e2cd44d97, f0b0738ba95731eeafd11352c74f8b48951f67dc.
Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to Linux Linux 9cc5761b8f28f9cef72061094eb5e37e2cd44d97, f0b0738ba95731eeafd11352c74f8b48951f67dc or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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).

—No exploit Fix available

EUVD-2026-112002

Published: Oct 28, 2026
Updated: Oct 28, 2026
EPSS: 0.1% · 4th percentile
CWE: —

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 0 / 40 · —
CISA KEV: 0 / 30 · Not listed
EPSS: 0 / 30 · 0.1%

Get told when this record changes

Not in KEV: no record of exploitation in the wild
No public exploit code on record
A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

—

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

Linux Linux
- 7.1affected
- 9c87959601e80b39a45250e362e6ddfec17cb0fa and later · before f0b0738ba95731eeafd11352c74f8b48951f67dcaffected · git
- 9c87959601e80b39a45250e362e6ddfec17cb0fa and later · before 9cc5761b8f28f9cef72061094eb5e37e2cd44d97affected · git
- before 7.1not affected · semver
- 7.2.13 and later · up to and including 7.2.*not affected · semver
- 7.3 and laternot affected · original_commit_for_fix

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

Ecosystem	Package	Affected range	Fix
Debian:14	linux	from 0	—

Same product

linux: all records

Other highest-scoring records for the same primary product.

CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation
40Plan
CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment
40Plan
CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()
40Plan

Published before and after this one in the same product

← EarlierCVE-2026-99100Oct 28, 2026 · wifi: p54: validate firmware record lengths
0Monitor
← EarlierCVE-2026-99101Oct 28, 2026 · ntfs: move attribute payload before shrinking its record
0Monitor
Later →CVE-2026-99103Oct 28, 2026 · workqueue: Fix unbound pool lifetime for pending pwqs
0Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / package	Fixed version	Source
Linux Linux	9cc5761b8f28f9cef72061094eb5e37e2cd44d97	Vendor (CNA)
Linux Linux	f0b0738ba95731eeafd11352c74f8b48951f67dc	Vendor (CNA)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

PublishedOct 28, 2026
Fix recordedOct 28, 2026same day
TodayNov 5, 2026+8 d

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).