CVE-2025-38615: fs/ntfs3: cancle set bad inode after removing name fails

Severity: medium (CVSS 5.5 v3.1)
Exploited in the wild: not listed in CISA KEV
EPSS: 0.2% probability of exploitation in the next 30 days
Public exploit or detection template: none known
Published: 2025-08-19 · updated 2026-10-30

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

Affected products

Linux kernel: from 5.15 before 6.6.102; from 6.7 before 6.12.42; from 6.13 before 6.15.10; from 6.16 before 6.16.1 — fixed in 6.6.102, 6.12.42, 6.15.10, 6.16.1
Linux: 5.15 — fixed in 6.17

How to fix

Upgrade to a fixed version: Linux kernel 6.6.102, 6.12.42, 6.15.10, 6.16.1; Linux 6.17. Check the vendor advisory for mitigations.

References

Get alerted when CVE-2025-38615 or the next vulnerability affects your stack