<?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://cve.radiocsirt.org</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>Wed, 07 Oct 2026 13:55:13 +0000</lastBuildDate>
    <item>
      <title>CVE-2024-42104 — nilfs2: add missing check for inode numbers on directory entries</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2024-42104</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: add missing check for inode numbers on directory entries&lt;/p&gt;
&lt;p&gt;Syzbot reported that mounting and unmounting a specific pattern of
corrupted nilfs2 filesystem images causes a use-after-free of metadata
file inodes, which triggers a kernel bug in lru_add_fn().&lt;/p&gt;
&lt;p&gt;As Jan Kara pointed out, this is because the link count of a metadata file
gets corrupted to 0, and nilfs_evict_inode(), which is called from iput(),
tries to delete that inode (ifile inode in this case).&lt;/p&gt;
&lt;p&gt;The inconsistency occurs because directories containing the inode numbers
of these metadata files that should not be visible in the namespace are
read without checking.&lt;/p&gt;
&lt;p&gt;Fix this issue by treating the inode numbers of these internal files as
errors in the sanity check helper when reading directory folios/pages.&lt;/p&gt;
&lt;p&gt;Also thanks to Hillf Danton and Matthew Wilcox for their initial mm-layer
analysis.&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: add missing check for inode numbers on directory entries&lt;/p&gt;
&lt;p&gt;Syzbot reported that mounting and unmounting a specific pattern of
corrupted nilfs2 filesystem images causes a use-after-free of metadata
file inodes, which triggers a kernel bug in lru_add_fn().&lt;/p&gt;
&lt;p&gt;As Jan Kara pointed out, this is because the link count of a metadata file
gets corrupted to 0, and nilfs_evict_inode(), which is called from iput(),
tries to delete that inode (ifile inode in this case).&lt;/p&gt;
&lt;p&gt;The inconsistency occurs because directories containing the inode numbers
of these metadata files that should not be visible in the namespace are
read without checking.&lt;/p&gt;
&lt;p&gt;Fix this issue by treating the inode numbers of these internal files as
errors in the sanity check helper when reading directory folios/pages.&lt;/p&gt;
&lt;p&gt;Also thanks to Hillf Danton and Matthew Wilcox for their initial mm-layer
analysis.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2024-42104</guid>
    </item>
  </channel>
</rss>
