VulnerabilityPublished 28 Oct 2026

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

Affects Linux kernelSource CVE Database V5

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

Data as of 28 Oct 2026, 10:58 UTC

Severity

Unrated

Rated by Threat Radar · 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.

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–

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

References

Community reviews

Loading reviews…