CVE-2025-40067

fs/ntfs3: reject index allocation if $BITMAP is empty but blocks exist

HIGH
7.8
CVSS Score
Published: October 28, 2025 at 11:48 AM UTC
Updated: October 19, 2026 at 09:10 PM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH7.8
Exploit prediction
EPSS 0.2%

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

6.12.42 ≤ v < 6.12.536.15.10 ≤ v < 6.166.16.1 ≤ v < 6.176.6.102 ≤ v < 6.6.112358d4f821c03add421a4c49290538a705852ccf13ed2cc6a6e93fbeb8c0cafce1e7fb1f64a331dcc6.12.426.15.106.16.16.176.6.102a285395020780adac1ffbc844069c3d700bf007ab35a50d639ca5259466ef5fea85529bb4fb17d5bd99208b91933fd2a58ed9ed321af07dacd06ddc3
Vendor states this is fixed in 039ddf353cc33f6546a87ec1ac3210637d714bec (fixed)
Vendor states this is fixed in 0dc7117da8f92dd5fe077d712a756eccbe377d40 (fixed)
Vendor states this is fixed in 978aac54e93ea35aab20b32ae393d3d33964e7ae (fixed)
Vendor states this is fixed in be66551da203862c689c12e1d35ce87217c017c1 (fixed)
Vendor states this is fixed in 6.12.53 (unaffected)
Affected range stops below 6.16, so it looks safe — our inference, not a vendor statement
Vendor states this is fixed in 6.17 (unaffected)
Vendor states this is fixed in 6.17.3 (unaffected)
Vendor states this is fixed in 6.18 (unaffected)
Vendor states this is fixed in 6.6.112 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

CVSS

7.8HIGHLinux
Vector?

Quick Info

StatusDEFERRED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card