VulnerabilityPublished 28 Oct 2026

CVE-2026-99107: Linux kernel · ntfs: fix incorrect MFT record pointer passed to ntfs_attr_record_resize

Affects Linux kernelSource CVE Database V5

Not known to be exploited : upgrade to 8d139e3635c86e2c97c78d55538ce0b00b6d9986 or 0a9122cada749447dfb6d67aa3fed4ee1982231c 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 8d139e3635c86e2c97c78d55538ce0b00b6d9986, 0a9122cada749447dfb6d67aa3fed4ee1982231c

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 8d139e3635c86e2c97c78d55538ce0b00b6d9986 or 0a9122cada749447dfb6d67aa3fed4ee1982231c.

Affected software

Product	Affected	Fixed in
LinuxLinux	Affected ≥ fc053f05ca282a5e760b41f6560ac835c4e28037, < 8d139e3635c86e2c97c78d55538ce0b00b6d9986	Fixed in 8d139e3635c86e2c97c78d55538ce0b00b6d9986
LinuxLinux	Affected ≥ fc053f05ca282a5e760b41f6560ac835c4e28037, < 0a9122cada749447dfb6d67aa3fed4ee1982231c	Fixed in 0a9122cada749447dfb6d67aa3fed4ee1982231c
LinuxLinux	Affected =7.1	Fixed in–

Description

In the Linux kernel, the following vulnerability has been resolved: ntfs: fix incorrect MFT record pointer passed to ntfs_attr_record_resize ntfs_new_attr_flags() passes the wrong MFT record to ntfs_attr_record_resize(). When the attribute is in an extent record, ctx->mrec points to the extent but the function receives the base record pointer m, causing incorrect size calculations in memmove. Fix by passing ctx->mrec (the actual MFT record containing the attribute) instead of m (the base MFT record) to ntfs_attr_record_resize().

References

Community reviews

Loading reviews…