CVE-2025-40067 json
fs/ntfs3: reject index allocation if $BITMAP is empty but blocks exist
published 2025-10-28 12 mo ago modified 2026-10-30 10 d ago also EUVD-2025-36461
- cvss
- 7.8
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 5%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- Linux Linux 6.6.112, 6.12.53, 6.16, 6.17, 6.17.3, 6.18
- linux Debian 13 6.12.57-1
- linux Debian 14 6.17.6-1
debian advisories DEBIAN-CVE-2025-40067
- linux Ubuntu 24.04 LTS 6.8.0-106.106
- linux Ubuntu 25.10 6.17.0-14.14
- linux-aws Ubuntu 24.04 LTS 6.8.0-1050.53
- linux-aws Ubuntu 25.10 6.17.0-1007.7
- linux-gcp Ubuntu 24.04 LTS 6.8.0-1052.55
- linux-gcp Ubuntu 25.10 6.17.0-1007.7
- linux-gke Ubuntu 24.04 LTS 6.8.0-1048.53
- linux-ibm Ubuntu 24.04 LTS 6.8.0-1049.49
ubuntu advisories UBUNTU-CVE-2025-40067
Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
- kernel-source-longterm openSUSE Tumbleweed 6.18.16-1.1
- kernel-source openSUSE Tumbleweed 6.17.7-1.1
opensuse advisories openSUSE-SU-2026:10301-1openSUSE-SU-2025:15702-1
- git.kernel.org/stable/c/aab2e34b139f6df71ab2b1adeec9927c206adc79 commit
- git.kernel.org/stable/c/978aac54e93ea35aab20b32ae393d3d33964e7ae commit
- git.kernel.org/stable/c/be66551da203862c689c12e1d35ce87217c017c1 commit
- git.kernel.org/stable/c/039ddf353cc33f6546a87ec1ac3210637d714bec commit
- git.kernel.org/stable/c/0dc7117da8f92dd5fe077d712a756eccbe377d40 commit
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2025-40067 updated
kernel: fs/ntfs3: reject index allocation if $BITMAP is empty but blocks exist
-
Red Hat Enterprise Linux 6 perf, kernel, python-perf, kernel-kdump, kernel-firmware, kernel-bootwrapper, +1 more Red Hat Enterprise Linux 7 perf, kernel, bpftool, kernel-rt, python-perf, kernel-kdump, +8 more Red Hat Enterprise Linux 8 perf, kernel, bpftool, kernel-rt, kernel-core, kernel-tools, +29 more Red Hat Enterprise Linux 9 rv, perf, rtla, kernel, bpftool, libperf, +83 more Red Hat Enterprise Linux 10 kernelnot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
0.16% chance of exploitation in the next 30 days, higher than 5% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 7.8 | CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H |
Affected products
- Linux Linux
Classification
- Technology feeds
References
- git.kernel.org /stable/c/aab2e34b139f6df71ab2b1adeec9927c206adc79
- git.kernel.org /stable/c/978aac54e93ea35aab20b32ae393d3d33964e7ae
- git.kernel.org /stable/c/be66551da203862c689c12e1d35ce87217c017c1
- git.kernel.org /stable/c/039ddf353cc33f6546a87ec1ac3210637d714bec
- git.kernel.org /stable/c/0dc7117da8f92dd5fe077d712a756eccbe377d40
Sources
- CVE List CVE-2025-40067
- NVD CVE-2025-40067
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.