CVE-2025-38615fs/ntfs3: cancle set bad inode after removing name fails
- 7.8HighCVSS base score
- 0.19%Exploitation in 30 daysEPSS · top 91% 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: cancle set bad inode after removing name fails The reproducer uses a file0 on a ntfs3 file system with a corrupted i_link. When renaming, the file0's inode is marked as a bad inode because the file name cannot be deleted. The underlying bug is that make_bad_inode() is called on a live inode. In some cases it's "icache lookup finds a normal inode, d_splice_alias() is called to attach it to dentry, while another thread decides to call make_bad_inode() on it - that would evict it from icache, but we'd already found it there earlier". In some it's outright "we have an inode attached to dentry - that's how we got it in the first place; let's call make_bad_inode() on it just for shits and giggles".
Timeline
ID reserved
By Linux
- 4 months later
· 4 months later
Published
- 15 months later
· 15 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:L/UI:N/S:U/C:H/I:H/A:H |
| NVDNVD · Modified | 3.1 | Medium5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
- EPSS (exploitation in 30 days)
- 0.19% · top 91% of all CVEs (17 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 78ab59fee07f22464f32eafebab2bd97ba94ff2d – < 47856e10f8d5e066aa26b1f9c02d933fe0620399
- affected 78ab59fee07f22464f32eafebab2bd97ba94ff2d – < b35a50d639ca5259466ef5fea85529bb4fb17d5b
- affected 78ab59fee07f22464f32eafebab2bd97ba94ff2d – < 3ed2cc6a6e93fbeb8c0cafce1e7fb1f64a331dcc
- affected 78ab59fee07f22464f32eafebab2bd97ba94ff2d – < 358d4f821c03add421a4c49290538a705852ccf1
- affected 78ab59fee07f22464f32eafebab2bd97ba94ff2d – < a285395020780adac1ffbc844069c3d700bf007a
- affected 78ab59fee07f22464f32eafebab2bd97ba94ff2d – < d99208b91933fd2a58ed9ed321af07dacd06ddc3
- affected 5.15
- unaffected < 5.15
- unaffected 6.1.191 – ≤ 6.1.*
- unaffected 6.6.102 – ≤ 6.6.*
- unaffected 6.12.42 – ≤ 6.12.*
- unaffected 6.15.10 – ≤ 6.15.*
- unaffected 6.16.1 – ≤ 6.16.*
- unaffected 6.17 – ≤ *
References
References6
- https://git.kernel.org/stable/c/47856e10f8d5e066aa26b1f9c02d933fe0620399 (opens in a new tab)
- https://git.kernel.org/stable/c/b35a50d639ca5259466ef5fea85529bb4fb17d5b (opens in a new tab)
- https://git.kernel.org/stable/c/3ed2cc6a6e93fbeb8c0cafce1e7fb1f64a331dcc (opens in a new tab)
- https://git.kernel.org/stable/c/358d4f821c03add421a4c49290538a705852ccf1 (opens in a new tab)
- https://git.kernel.org/stable/c/a285395020780adac1ffbc844069c3d700bf007a (opens in a new tab)
- https://git.kernel.org/stable/c/d99208b91933fd2a58ed9ed321af07dacd06ddc3 (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-27935 (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-38615)Record last updated .