CVE-2026-99101
ntfs: move attribute payload before shrinking its record
What happened?
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.
Affected software and versions
| Software | Version information | Fixed version |
|---|---|---|
| LinuxLinux | affected: 47503f989736d6c4c9f8bfca1c28d267473ccd4b to < 7dc2c524608039d1b082a0087f7aa0751edd4ffb; affected: 47503f989736d6c4c9f8bfca1c28d267473ccd4b to < 0ab6dc1ac4601c8d79e5448a024daed6b0c5ef64 | See vendor advisory |
| LinuxLinux | affected: 7.1; unaffected: 0 to < 7.1; unaffected: 7.2.13 to ≤ 7.2.*; unaffected: 7.3 to ≤ * | See vendor advisory |
Version information comes from the source record and can include unaffected products and exceptions. Distribution packages may contain backported fixes: an older upstream version alone does not prove a server is affected.
Is it being exploited?
This CVE was not listed in the CISA catalogue at our last retrieval. This does not establish that exploitation is absent.
How to respond
- Confirm the product, installed package version, and any configuration requirements in the vendor advisory.
- Follow the vendor’s remediation or workaround guidance in the references below. Structured fixed-version data is unavailable here; the publisher’s description may include a fix or workaround.
- Restart affected services if required, then verify the running version. Known exploitation may warrant investigation as well as patching.