VulnerabilityPublished 28 Oct 2026

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

Source GCVE Database

Authoritative record:CVE-2026-99102

Not known to be exploited : upgrade to f0b0738ba95731eeafd11352c74f8b48951f67dc or 9cc5761b8f28f9cef72061094eb5e37e2cd44d97 when convenient.

Data as of 28 Oct 2026, 14:28 UTC

Severity

Medium

Rated Medium by Threat Radar's AI analysis · CVSS not yet scored by NVD

Patch: Available – fixed in f0b0738ba95731eeafd11352c74f8b48951f67dc, 9cc5761b8f28f9cef72061094eb5e37e2cd44d97

Exploitation evidence

Disclosed: evidence found.
CVE published 28 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

ghsa-pchj-j532-7cm6

What to do

Upgrade Linux kernel to f0b0738ba95731eeafd11352c74f8b48951f67dc or 9cc5761b8f28f9cef72061094eb5e37e2cd44d97.

Affected software

Product	Affected	Fixed in
LinuxLinux	Affected ≥ 9c87959601e80b39a45250e362e6ddfec17cb0fa, < f0b0738ba95731eeafd11352c74f8b48951f67dc	Fixed in f0b0738ba95731eeafd11352c74f8b48951f67dc
LinuxLinux	Affected ≥ 9c87959601e80b39a45250e362e6ddfec17cb0fa, < 9cc5761b8f28f9cef72061094eb5e37e2cd44d97	Fixed in 9cc5761b8f28f9cef72061094eb5e37e2cd44d97
LinuxLinux	Affected =7.1	Fixed in–

AI-suggested

A fix has been implemented that ensures the invalidate_lock is taken exclusively around the entire resize operation in ntfs_setattr_size(). Users should apply the official Linux kernel updates that include this fix to prevent the race condition and associated faults.

Description

A vulnerability in the Linux kernel's NTFS filesystem code involves improper locking in the ntfs_setattr_size() function. The function updates file size and resizes on-disk attributes without holding the required invalidate_lock, potentially causing race conditions with page faults. This can lead to spurious SIGBUS signals and inconsistent file size state during concurrent access.

References

Community reviews

Loading reviews…