fs/ntfs3: reject index allocation if $BITMAP is empty but blocks exist (CVE-2025-40067) | HOL Guard CVE

Unknown severity · Source severity not reportedCVE-2025-40067

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

Answer in brief

CVE-2025-40067 records a Unknown severity vulnerability in fs/ntfs3: reject index allocation if $BITMAP is empty but blocks exist. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Oct 28, 2025Updated Aug 5, 2026Source checked Sep 21, 2026First seen by HOL Aug 5, 2026Material review Aug 5, 2026

Upstream Advisory

Key facts

Risk: Unknown severitySource severity not reported
Exploitation: Not marked as known exploited
Affected software: 2 mapped packages or products
Fix availability: Available

Why this deserves its current priority

A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
Linux/Linuxgeneric	>=b35a50d639ca5259466ef5fea85529bb4fb17d5b <978aac54e93ea35aab20b32ae393d3d33964e7ae \|\| >=3ed2cc6a6e93fbeb8c0cafce1e7fb1f64a331dcc <be66551da203862c689c12e1d35ce87217c017c1 \|\| >=d99208b91933fd2a58ed9ed321af07dacd06ddc3 <039ddf353cc33f6546a87ec1ac3210637d714bec \|\| >=d99208b91933fd2a58ed9ed321af07dacd06ddc3 <0dc7117da8f92dd5fe077d712a756eccbe377d40 \|\| 358d4f821c03add421a4c49290538a705852ccf1 \|\| a285395020780adac1ffbc844069c3d700bf007a \|\| >=6.6.102 <6.6.112 \|\| >=6.12.42 <6.12.53 \|\| >=6.15.10 <6.16 \|\| >=6.16.1 <6.17	978aac54e93ea35aab20b32ae393d3d33964e7ae, be66551da203862c689c12e1d35ce87217c017c1, 039ddf353cc33f6546a87ec1ac3210637d714bec, 0dc7117da8f92dd5fe077d712a756eccbe377d40, 6.6.112, 6.12.53, 6.16, 6.17
Linux/Linuxgeneric	6.17	Not reported

Recommended response

Check inventory. Check lockfiles and deployed manifests for Linux/Linux, Linux/Linux.
Review the reported fix. Update Linux/Linux to 978aac54e93ea35aab20b32ae393d3d33964e7ae if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

Published upstream
Oct 28, 2025
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Aug 5, 2026

Sources and claim methodology

Upstream source 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.

Quoted source text, attributed separately from HOL analysis.