CVE-2025-40067fs/ntfs3: reject index allocation if $BITMAP is empty but blocks exist
- 7.8HighCVSS base score
- 0.16%Exploitation in 30 daysEPSS · top 94% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
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.
Timeline
ID reserved
By Linux
- 7 months later
· 7 months later
Published
- 12 months later
· 12 months later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| LinuxCNA (assigner) | 3.1 | High7.8 | CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H |
| NVDNVD · Deferred | 3.1 | High7.8 | CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H |
- EPSS (exploitation in 30 days)
- 0.16% · top 94% of all CVEs (16 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.8.
Affected products
- affected 47856e10f8d5e066aa26b1f9c02d933fe0620399 – < aab2e34b139f6df71ab2b1adeec9927c206adc79
- affected b35a50d639ca5259466ef5fea85529bb4fb17d5b – < 978aac54e93ea35aab20b32ae393d3d33964e7ae
- affected 3ed2cc6a6e93fbeb8c0cafce1e7fb1f64a331dcc – < be66551da203862c689c12e1d35ce87217c017c1
- affected d99208b91933fd2a58ed9ed321af07dacd06ddc3 – < 039ddf353cc33f6546a87ec1ac3210637d714bec
- affected d99208b91933fd2a58ed9ed321af07dacd06ddc3 – < 0dc7117da8f92dd5fe077d712a756eccbe377d40
- affected 358d4f821c03add421a4c49290538a705852ccf1
- affected a285395020780adac1ffbc844069c3d700bf007a
- affected 6.6.102 – < 6.6.112
- affected 6.12.42 – < 6.12.53
- affected 6.15.10 – < 6.16
- affected 6.16.1 – < 6.17
- affected 6.17
- unaffected < 6.17
- unaffected 6.6.112 – ≤ 6.6.*
- unaffected 6.12.53 – ≤ 6.12.*
- unaffected 6.17.3 – ≤ 6.17.*
- unaffected 6.18 – ≤ *
References
References5
- https://git.kernel.org/stable/c/aab2e34b139f6df71ab2b1adeec9927c206adc79 (opens in a new tab)
- https://git.kernel.org/stable/c/978aac54e93ea35aab20b32ae393d3d33964e7ae (opens in a new tab)
- https://git.kernel.org/stable/c/be66551da203862c689c12e1d35ce87217c017c1 (opens in a new tab)
- https://git.kernel.org/stable/c/039ddf353cc33f6546a87ec1ac3210637d714bec (opens in a new tab)
- https://git.kernel.org/stable/c/0dc7117da8f92dd5fe077d712a756eccbe377d40 (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2025-36461 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2025-40067)Record last updated .