https://vulnerability.circl.lu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Fri, 02 Oct 2026 01:49:07 +0000 https://vulnerability.circl.lu/vuln/cve-2025-38615 <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>fs/ntfs3: cancle set bad inode after removing name fails</p> <p>The reproducer uses a file0 on a ntfs3 file system with a corrupted i_link. When renaming, the file0&#39;s inode is marked as a bad inode because the file name cannot be deleted.</p> <p>The underlying bug is that make_bad_inode() is called on a live inode. In some cases it&#39;s &#34;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&#39;d already found it there earlier&#34;. In some it&#39;s outright &#34;we have an inode attached to dentry - that&#39;s how we got it in the first place; let&#39;s call make_bad_inode() on it just for shits and giggles&#34;.</p> <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>fs/ntfs3: cancle set bad inode after removing name fails</p> <p>The reproducer uses a file0 on a ntfs3 file system with a corrupted i_link. When renaming, the file0&#39;s inode is marked as a bad inode because the file name cannot be deleted.</p> <p>The underlying bug is that make_bad_inode() is called on a live inode. In some cases it&#39;s &#34;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&#39;d already found it there earlier&#34;. In some it&#39;s outright &#34;we have an inode attached to dentry - that&#39;s how we got it in the first place; let&#39;s call make_bad_inode() on it just for shits and giggles&#34;.</p> https://vulnerability.circl.lu/vuln/cve-2025-38615