fs/ntfs3: reject index allocation if $BITMAP is empty but blocks exist
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
358d4f821c03add421a4c49290538a705852ccf1| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
fs/ntfs3: reject index allocation if $BITMAP is empty but blocks exist
Index allocation requires at least one bit in the $BITMAP attribute to track usage of index entries. If the bitmap is empty while index blocks are already present, this reflects on-disk corruption.
syzbot triggered this condition using a malformed NTFS image. During a rename() operation involving a long filename (which spans multiple index entries), the empty bitmap allowed the name to be added without valid tracking. Subsequent deletion of the original entry failed with -ENOENT, due to unexpected index state.
Reject such cases by verifying that the bitmap is not empty when index blocks exist.
From the CVE record · Linux
The Linux kernel's NTFS3 driver can mishandle a malformed NTFS image whose index bitmap is empty even though index blocks exist. A rename involving a long filename can leave the index in an unexpected state, causing deletion of the original entry to fail. The input does not specify network access, authentication requirements, or user interaction.
Engineers running Linux kernels with the NTFS3 driver should check their versions against the vendor advisory; affected versions are not specified.