<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://vulnerability.circl.lu</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Fri, 02 Oct 2026 12:29:54 +0000</lastBuildDate>
    <item>
      <title>CVE-2024-53690 — nilfs2: prevent use of deleted inode</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2024-53690</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;nilfs2: prevent use of deleted inode&lt;/p&gt;
&lt;p&gt;syzbot reported a WARNING in nilfs_rmdir. [1]&lt;/p&gt;
&lt;p&gt;Because the inode bitmap is corrupted, an inode with an inode number that
should exist as a &amp;#34;.nilfs&amp;#34; file was reassigned by nilfs_mkdir for &amp;#34;file0&amp;#34;,
causing an inode duplication during execution.  And this causes an
underflow of i_nlink in rmdir operations.&lt;/p&gt;
&lt;p&gt;The inode is used twice by the same task to unmount and remove directories
&amp;#34;.nilfs&amp;#34; and &amp;#34;file0&amp;#34;, it trigger warning in nilfs_rmdir.&lt;/p&gt;
&lt;p&gt;Avoid to this issue, check i_nlink in nilfs_iget(), if it is 0, it means
that this inode has been deleted, and iput is executed to reclaim it.&lt;/p&gt;
&lt;p&gt;[1]
WARNING: CPU: 1 PID: 5824 at fs/inode.c:407 drop_nlink+0xc4/0x110 fs/inode.c:407
...
Call Trace:
 &amp;lt;TASK&amp;gt;
 nilfs_rmdir+0x1b0/0x250 fs/nilfs2/namei.c:342
 vfs_rmdir+0x3a3/0x510 fs/namei.c:4394
 do_rmdir+0x3b5/0x580 fs/namei.c:4453
 __do_sys_rmdir fs/namei.c:4472 [inline]
 __se_sys_rmdir fs/namei.c:4470 [inline]
 __x64_sys_rmdir+0x47/0x50 fs/namei.c:4470
 do_syscall_x64 arch/x86/entry/common.c:52 [inline]
 do_syscall_64+0xf3/0x230 arch/x86/entry/common.c:83
 entry_SYSCALL_64_after_hwframe+0x77/0x7f&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;nilfs2: prevent use of deleted inode&lt;/p&gt;
&lt;p&gt;syzbot reported a WARNING in nilfs_rmdir. [1]&lt;/p&gt;
&lt;p&gt;Because the inode bitmap is corrupted, an inode with an inode number that
should exist as a &amp;#34;.nilfs&amp;#34; file was reassigned by nilfs_mkdir for &amp;#34;file0&amp;#34;,
causing an inode duplication during execution.  And this causes an
underflow of i_nlink in rmdir operations.&lt;/p&gt;
&lt;p&gt;The inode is used twice by the same task to unmount and remove directories
&amp;#34;.nilfs&amp;#34; and &amp;#34;file0&amp;#34;, it trigger warning in nilfs_rmdir.&lt;/p&gt;
&lt;p&gt;Avoid to this issue, check i_nlink in nilfs_iget(), if it is 0, it means
that this inode has been deleted, and iput is executed to reclaim it.&lt;/p&gt;
&lt;p&gt;[1]
WARNING: CPU: 1 PID: 5824 at fs/inode.c:407 drop_nlink+0xc4/0x110 fs/inode.c:407
...
Call Trace:
 &amp;lt;TASK&amp;gt;
 nilfs_rmdir+0x1b0/0x250 fs/nilfs2/namei.c:342
 vfs_rmdir+0x3a3/0x510 fs/namei.c:4394
 do_rmdir+0x3b5/0x580 fs/namei.c:4453
 __do_sys_rmdir fs/namei.c:4472 [inline]
 __se_sys_rmdir fs/namei.c:4470 [inline]
 __x64_sys_rmdir+0x47/0x50 fs/namei.c:4470
 do_syscall_x64 arch/x86/entry/common.c:52 [inline]
 do_syscall_64+0xf3/0x230 arch/x86/entry/common.c:83
 entry_SYSCALL_64_after_hwframe+0x77/0x7f&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2024-53690</guid>
    </item>
  </channel>
</rss>
