<?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>Sun, 04 Oct 2026 22:11:32 +0000</lastBuildDate>
    <item>
      <title>CVE-2024-46701 — libfs: fix infinite directory reads for offset dir</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2024-46701</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;libfs: fix infinite directory reads for offset dir&lt;/p&gt;
&lt;p&gt;After we switch tmpfs dir operations from simple_dir_operations to
simple_offset_dir_operations, every rename happened will fill new dentry
to dest dir&amp;#39;s maple tree(&amp;amp;SHMEM_I(inode)-&amp;gt;dir_offsets-&amp;gt;mt) with a free
key starting with octx-&amp;gt;newx_offset, and then set newx_offset equals to
free key + 1. This will lead to infinite readdir combine with rename
happened at the same time, which fail generic/736 in xfstests(detail show
as below).&lt;/p&gt;
&lt;p&gt;1. create 5000 files(1 2 3...) under one dir
2. call readdir(man 3 readdir) once, and get one entry
3. rename(entry, &amp;#34;TEMPFILE&amp;#34;), then rename(&amp;#34;TEMPFILE&amp;#34;, entry)
4. loop 2~3, until readdir return nothing or we loop too many
   times(tmpfs break test with the second condition)&lt;/p&gt;
&lt;p&gt;We choose the same logic what commit 9b378f6ad48cf (&amp;#34;btrfs: fix infinite
directory reads&amp;#34;) to fix it, record the last_index when we open dir, and
do not emit the entry which index &amp;gt;= last_index. The file-&amp;gt;private_data
now used in offset dir can use directly to do this, and we also update
the last_index when we llseek the dir file.&lt;/p&gt;
&lt;p&gt;[brauner: only update last_index after seek when offset is zero like Jan suggested]&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;libfs: fix infinite directory reads for offset dir&lt;/p&gt;
&lt;p&gt;After we switch tmpfs dir operations from simple_dir_operations to
simple_offset_dir_operations, every rename happened will fill new dentry
to dest dir&amp;#39;s maple tree(&amp;amp;SHMEM_I(inode)-&amp;gt;dir_offsets-&amp;gt;mt) with a free
key starting with octx-&amp;gt;newx_offset, and then set newx_offset equals to
free key + 1. This will lead to infinite readdir combine with rename
happened at the same time, which fail generic/736 in xfstests(detail show
as below).&lt;/p&gt;
&lt;p&gt;1. create 5000 files(1 2 3...) under one dir
2. call readdir(man 3 readdir) once, and get one entry
3. rename(entry, &amp;#34;TEMPFILE&amp;#34;), then rename(&amp;#34;TEMPFILE&amp;#34;, entry)
4. loop 2~3, until readdir return nothing or we loop too many
   times(tmpfs break test with the second condition)&lt;/p&gt;
&lt;p&gt;We choose the same logic what commit 9b378f6ad48cf (&amp;#34;btrfs: fix infinite
directory reads&amp;#34;) to fix it, record the last_index when we open dir, and
do not emit the entry which index &amp;gt;= last_index. The file-&amp;gt;private_data
now used in offset dir can use directly to do this, and we also update
the last_index when we llseek the dir file.&lt;/p&gt;
&lt;p&gt;[brauner: only update last_index after seek when offset is zero like Jan suggested]&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2024-46701</guid>
    </item>
  </channel>
</rss>
