<?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>Tue, 29 Sep 2026 16:00:41 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-89786 — ext4: fix out-of-bounds read in ext4_read_inline_dir()</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-89786</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;ext4: fix out-of-bounds read in ext4_read_inline_dir()&lt;/p&gt;
&lt;p&gt;ext4_read_inline_dir() can read a dirent header past the end of its inline
buffer, triggering a slab-out-of-bounds read during getdents64():&lt;/p&gt;
&lt;p&gt;BUG: KASAN: slab-out-of-bounds in __ext4_check_dir_entry
  Read of size 2 at addr ffff88800f3dd23c by task exploit/148
   ...
   __ext4_check_dir_entry
   ext4_read_inline_dir
   iterate_dir&lt;/p&gt;
&lt;p&gt;The dirent payload lives in a buffer of exactly inline_size bytes:&lt;/p&gt;
&lt;p&gt;dir_buf = kmalloc(inline_size, GFP_NOFS);&lt;/p&gt;
&lt;p&gt;but iteration runs in a position space extra_offset bytes larger
(extra_size = extra_offset + inline_size) so the synthetic &amp;#34;.&amp;#34; and &amp;#34;..&amp;#34;
land at their block-dir offsets. A dirent is formed at &amp;#34;dir_buf + pos -
extra_offset&amp;#34;, yet the ext4_check_dir_entry() length argument uses the
larger extra_size. A position whose dirent header would extend past
extra_size is therefore accepted, and the rescan loop&amp;#39;s rec_len probe and
ext4_check_dir_entry() dereference de-&amp;gt;rec_len before the entry is rejected.&lt;/p&gt;
&lt;p&gt;Reject a position whose minimum-size dirent header would not fit within
extra_size before forming de, in both the rescan and main loops, and pass
inline_size rather than extra_size to ext4_check_dir_entry() so the length
check matches the physical buffer.&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;ext4: fix out-of-bounds read in ext4_read_inline_dir()&lt;/p&gt;
&lt;p&gt;ext4_read_inline_dir() can read a dirent header past the end of its inline
buffer, triggering a slab-out-of-bounds read during getdents64():&lt;/p&gt;
&lt;p&gt;BUG: KASAN: slab-out-of-bounds in __ext4_check_dir_entry
  Read of size 2 at addr ffff88800f3dd23c by task exploit/148
   ...
   __ext4_check_dir_entry
   ext4_read_inline_dir
   iterate_dir&lt;/p&gt;
&lt;p&gt;The dirent payload lives in a buffer of exactly inline_size bytes:&lt;/p&gt;
&lt;p&gt;dir_buf = kmalloc(inline_size, GFP_NOFS);&lt;/p&gt;
&lt;p&gt;but iteration runs in a position space extra_offset bytes larger
(extra_size = extra_offset + inline_size) so the synthetic &amp;#34;.&amp;#34; and &amp;#34;..&amp;#34;
land at their block-dir offsets. A dirent is formed at &amp;#34;dir_buf + pos -
extra_offset&amp;#34;, yet the ext4_check_dir_entry() length argument uses the
larger extra_size. A position whose dirent header would extend past
extra_size is therefore accepted, and the rescan loop&amp;#39;s rec_len probe and
ext4_check_dir_entry() dereference de-&amp;gt;rec_len before the entry is rejected.&lt;/p&gt;
&lt;p&gt;Reject a position whose minimum-size dirent header would not fit within
extra_size before forming de, in both the rescan and main loops, and pass
inline_size rather than extra_size to ext4_check_dir_entry() so the length
check matches the physical buffer.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-89786</guid>
    </item>
  </channel>
</rss>
