Vulnerability · CVE-2025-38615
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
Published Aug 19, 2025 · catalog updated Aug 5, 2026 · Linux Linux
Check this week
CVE-2025-38615 is not in CISA KEV. FIRST estimates a 18.00% chance of exploitation in the next 30 days. Check whether you run Linux Linux.
Gaps on this record
- No vendor fix or required action is stored. Compare the linked advisory before you change production.
- Severity
- High7.8
- Known exploitation
- Not in CISA/VulnCheck KEV
- EPSS
- 18.00%
- Remediation
- Version ranges on file
- Affected products
- vendor Linux Linux 78ab59fee07f22464f32eafebab2bd97ba94ff2d <358d4f821c03add421a4c49290538a705852ccf1
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 t
Are you affected?
Enter the version you run. The result uses only the ranges stored on this record.
The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.
- vendor Linux Linux 78ab59fee07f22464f32eafebab2bd97ba94ff2d <358d4f821c03add421a4c49290538a705852ccf178ab59fee07f22464f32eafebab2bd97ba94ff2d <358d4f821c03add421a4c49290538a705852ccf1
How to fix CVE-2025-38615
Recommended remediation
Affected version ranges suggest a fixed boundary. Verify against the vendor advisory for your release.
Official advisories
What to do
Three questions, each answered from this record only. Confirm the vendor advisory before you patch.
Should you patch?
CVE-2025-38615 is not in CISA KEV. FIRST estimates a 18.00% chance of exploitation in the next 30 days. Check whether you run Linux Linux.
Which versions are affected?
Compare what you have installed with Linux Linux 78ab59fee07f22464f32eafebab2bd97ba94ff2d <358d4f821c03add421a4c49290538a705852ccf1 78ab59fee07f22464f32eafebab2bd97ba94ff2d <358d4f821c03add421a4c49290538a705852ccf1. Compare the installed version with the linked vendor advisory before you change production.
What should an analyst verify?
No weakness class is stored. EPSS 18.00%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.
Code
The project this record applies to. Exploit listings stay in References.
Timeline
Detection, updates, and resolution for this record.
Aug 19, 2025 · EUVD
Detected
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 lo
Aug 5, 2026 · EUVD
Updated
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 lo
Sources
- CVE.orgVulnerability recordCVE-2025-38615
Official CVE identifier
cve.org - EUVDVulnerability recordEUVD-2025-27935
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
euvd.enisa.europa.eu
References
Freshness
Last verified in this catalog Aug 5, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.