<?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>Sun, 04 Oct 2026 18:30:39 +0000</lastBuildDate>
    <item>
      <title>CVE-2024-50202 — nilfs2: propagate directory read errors from nilfs_find_entry()</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2024-50202</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: propagate directory read errors from nilfs_find_entry()&lt;/p&gt;
&lt;p&gt;Syzbot reported that a task hang occurs in vcs_open() during a fuzzing
test for nilfs2.&lt;/p&gt;
&lt;p&gt;The root cause of this problem is that in nilfs_find_entry(), which
searches for directory entries, ignores errors when loading a directory
page/folio via nilfs_get_folio() fails.&lt;/p&gt;
&lt;p&gt;If the filesystem images is corrupted, and the i_size of the directory
inode is large, and the directory page/folio is successfully read but
fails the sanity check, for example when it is zero-filled,
nilfs_check_folio() may continue to spit out error messages in bursts.&lt;/p&gt;
&lt;p&gt;Fix this issue by propagating the error to the callers when loading a
page/folio fails in nilfs_find_entry().&lt;/p&gt;
&lt;p&gt;The current interface of nilfs_find_entry() and its callers is outdated
and cannot propagate error codes such as -EIO and -ENOMEM returned via
nilfs_find_entry(), so fix it together.&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: propagate directory read errors from nilfs_find_entry()&lt;/p&gt;
&lt;p&gt;Syzbot reported that a task hang occurs in vcs_open() during a fuzzing
test for nilfs2.&lt;/p&gt;
&lt;p&gt;The root cause of this problem is that in nilfs_find_entry(), which
searches for directory entries, ignores errors when loading a directory
page/folio via nilfs_get_folio() fails.&lt;/p&gt;
&lt;p&gt;If the filesystem images is corrupted, and the i_size of the directory
inode is large, and the directory page/folio is successfully read but
fails the sanity check, for example when it is zero-filled,
nilfs_check_folio() may continue to spit out error messages in bursts.&lt;/p&gt;
&lt;p&gt;Fix this issue by propagating the error to the callers when loading a
page/folio fails in nilfs_find_entry().&lt;/p&gt;
&lt;p&gt;The current interface of nilfs_find_entry() and its callers is outdated
and cannot propagate error codes such as -EIO and -ENOMEM returned via
nilfs_find_entry(), so fix it together.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2024-50202</guid>
    </item>
  </channel>
</rss>
