CVE Catalog

CVE-2025-38615

HighCVSS 7.8
Published: Updated: Translated: NVD NIST

Exploitation Probability (EPSS)

Low risk
0.16%

6th percentile - higher than 6% of all known CVEs

Summary

In the Linux kernel ntfs3 filesystem, a vulnerability exists where a live inode is marked as bad after a file name removal fails. This can lead to icache inconsistencies and potentially a use-after-free.

Risk Assessment

A local attacker can cause filesystem inconsistency and potentially lead to system crash or privilege escalation through inode manipulation.

Recommendation

Apply the Linux kernel patch that prevents marking a live inode as bad after name removal failure. Update your system to a kernel version containing the fix.

Other vulnerabilities in Linux kernel

See all
Original NVD description (English source)

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".

Vulnerability data from NVD (NIST) · CISA KEV · EPSS