CVE-2025-38615
What it is
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".
At a glance
- Exploitability
- Can be exploited locally on the machine with a low-privilege account. High risk of data exposure, data tampering, service disruption.
- Exploit odds
- 0.2% chance of exploitation in the next 30 days (EPSS).
- Fix
- A patch, advisory or fixed version is referenced. Upgrade or apply it.
Timeline
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: 0.2% in the next 30 days (EPSS).
- Severity: 7.8 HIGH (CVSS).
- Fix: a patch or advisory is linked.
Details
- Published
- Last modified
- Exploit probability
- 0.2% · EPSS, next 30 days
- Record status
- Modified
Affected
- Linux Kernel < 6.6.102
- Linux Kernel < 6.12.42
- Linux Kernel < 6.15.10
- Linux Kernel < 6.16.1
Attack profile CVSS 3.1 · 7.8
- Attack vector
- Local
- Complexity
- Low
- Privileges needed
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
Raw vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2025-38615.md and follow it. Check whether this project is affected by CVE-2025-38615. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
Fix and advisories
- https://git.kernel.org/stable/c/358d4f821c03add421a4c49290538a705852ccf1
- https://git.kernel.org/stable/c/3ed2cc6a6e93fbeb8c0cafce1e7fb1f64a331dcc
- https://git.kernel.org/stable/c/a285395020780adac1ffbc844069c3d700bf007a
- https://git.kernel.org/stable/c/b35a50d639ca5259466ef5fea85529bb4fb17d5b
- https://git.kernel.org/stable/c/d99208b91933fd2a58ed9ed321af07dacd06ddc3
References
- https://git.kernel.org/stable/c/358d4f821c03add421a4c49290538a705852ccf1
- https://git.kernel.org/stable/c/3ed2cc6a6e93fbeb8c0cafce1e7fb1f64a331dcc
- https://git.kernel.org/stable/c/47856e10f8d5e066aa26b1f9c02d933fe0620399
- https://git.kernel.org/stable/c/a285395020780adac1ffbc844069c3d700bf007a
- https://git.kernel.org/stable/c/b35a50d639ca5259466ef5fea85529bb4fb17d5b
- https://git.kernel.org/stable/c/d99208b91933fd2a58ed9ed321af07dacd06ddc3