Acknowledged
Created: Oct 29, 2025
Updated: Oct 30, 2025
Found In Version: 10.24.33.1
Severity: Standard
Applicable for: Wind River Linux LTS 24
Component/s: Kernel
In the Linux kernel, the following vulnerability has been resolved:[EOL][EOL]fs/ntfs3: reject index allocation if $BITMAP is empty but blocks exist[EOL][EOL]Index allocation requires at least one bit in the $BITMAP attribute to[EOL]track usage of index entries. If the bitmap is empty while index blocks[EOL]are already present, this reflects on-disk corruption.[EOL][EOL]syzbot triggered this condition using a malformed NTFS image. During a[EOL]rename() operation involving a long filename (which spans multiple[EOL]index entries), the empty bitmap allowed the name to be added without[EOL]valid tracking. Subsequent deletion of the original entry failed with[EOL]-ENOENT, due to unexpected index state.[EOL][EOL]Reject such cases by verifying that the bitmap is not empty when index[EOL]blocks exist.