CVE-2025-38615
Last modified
CVE-2025-38615 is a medium-severity vulnerability rated 5.5/10 on the CVSS scale. 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".. EPSS estimates a 0.15% chance of exploitation in the next 30 days.
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".
Metrics
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux Kernel | >= 5.15, < 6.6.102 |
| Linux | Linux Kernel | >= 6.7, < 6.12.42 |
| Linux | Linux Kernel | >= 6.13, < 6.15.10 |
| Linux | Linux Kernel | >= 6.16, < 6.16.1 |
References
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2025-38615?
How severe is CVE-2025-38615?
How do I fix CVE-2025-38615?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2025
- CVE-2025-3861The Prevent Direct Access – Protect WordPress Files plugin f…5.4
- CVE-2025-38610In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-38611Rejected reason: This CVE ID has been rejected or withdrawn …
- CVE-2025-38612In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-38613In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-38614In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-38616In the Linux kernel, the following vulnerability has been re…7.1
- CVE-2025-38617In the Linux kernel, the following vulnerability has been re…4.7
- CVE-2025-38618In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2025-38619In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-3862Contest Gallery plugin for WordPress is vulnerable to Stored…5.4
- CVE-2025-38620In the Linux kernel, the following vulnerability has been re…7.8
Are you affected by CVE-2025-38615?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
