CVE-2025-40067
Description
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.
AI Insight
LLM-synthesized narrative grounded in this CVE's description and references.
Affected products
4- osv-coords3 versionspkg:linux/kernelpkg:rpm/opensuse/kernel-source-longterm&distro=openSUSE%20Tumbleweedpkg:rpm/opensuse/kernel-source&distro=openSUSE%20Tumbleweed
>= 6.6.102, < 6.6.112+ 2 more
- (no CPE)range: >= 6.6.102, < 6.6.112
- (no CPE)range: < 6.18.16-1.1
- (no CPE)range: < 6.17.7-1.1
Patches
Vulnerability mechanics
References
5- git.kernel.org/stable/c/039ddf353cc33f6546a87ec1ac3210637d714becnvd
- git.kernel.org/stable/c/0dc7117da8f92dd5fe077d712a756eccbe377d40nvd
- git.kernel.org/stable/c/978aac54e93ea35aab20b32ae393d3d33964e7aenvd
- git.kernel.org/stable/c/aab2e34b139f6df71ab2b1adeec9927c206adc79nvd
- git.kernel.org/stable/c/be66551da203862c689c12e1d35ce87217c017c1nvd
News mentions
0No linked articles in our index yet.