Live › vulnerability › CVE-2026-99101
Go to dashboardWhen the Linux kernel's NTFS driver clears compression or sparse state on a file, it resizes the attribute record before moving its payload, so the following attribute's bytes get copied into the mapping pairs. Re-enabling compression on an empty file then writes a malformed mapping pairs array to disk that ntfsck reports as a bad run length.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-28 11:32 UTC. All times on this page are UTC.
No product ranges from the sources yet.
Unknown from the sources.
Unknown from the sources.
Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
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.
This page as .md · .json · in your agent: get_signal("CVE-2026-99101")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.