Skip to main content
VulnerabilityPublished

CVE-2026-99101: Linux kernel · ntfs: move attribute payload before shrinking its record

Affects Linux kernelSource CVE Database V5

0

Not known to be exploited · fixed in 7dc2c524608039d1b082a0087f7aa0751edd4ffb : update Linux kernel 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 7dc2c524608039d1b082a0087f7aa0751edd4ffb, 7.2.13, 0ab6dc1ac4601c8d79e5448a024daed6b0c5ef64

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 28 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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.

What to do

Upgrade Linux kernel to 7dc2c524608039d1b082a0087f7aa0751edd4ffb, 7.2.13 or 0ab6dc1ac4601c8d79e5448a024daed6b0c5ef64.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • <7.2.13
Fixed in
  • 7dc2c524608039d1b082a0087f7aa0751edd4ffb
  • 7.2.13
  • 0ab6dc1ac4601c8d79e5448a024daed6b0c5ef64

Description

In the Linux kernel, the following vulnerability has been resolved: ntfs: move attribute payload before shrinking its record ntfs_new_attr_flags() resizes the non-resident attribute record before moving its name and mapping pairs to their shorter-header offsets when compression or sparse state is cleared. Shrinking the record first moves the following attribute over the tail of the old record. The subsequent memmove() therefore copies bytes from that following attribute instead of the old mapping pairs. Re-enabling compression on an empty file persists those bytes as a malformed mapping pairs array, which ntfsck reports as a missing or invalid run length. Move the payload before shrinking the record, while retaining the existing resize-before-move ordering when growing it.

References

Community reviews

Loading reviews…