CVE-2025-40067
In the Linux kernel, the following vulnerability has been resolved: …
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.
What to do now
- Check your exposureFind out whether the affected software runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Set the orderSystems that can be reached from the internet come first, then the rest.
References
- git.kernel.org/stable/c/039ddf353cc33f6546a87ec1ac3210637d714bec
- git.kernel.org/stable/c/0dc7117da8f92dd5fe077d712a756eccbe377d40
- git.kernel.org/stable/c/978aac54e93ea35aab20b32ae393d3d33964e7ae
- git.kernel.org/stable/c/be66551da203862c689c12e1d35ce87217c017c1
- git.kernel.org/stable/c/aab2e34b139f6df71ab2b1adeec9927c206adc79
- nvd.nist.gov/vuln/detail/CVE-2025-40067
- cve.org/CVERecord?id=CVE-2025-40067
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.