<?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 14:36:31 +0000</lastBuildDate>
    <item>
      <title>CVE-2025-38710 — gfs2: Validate i_depth for exhash directories</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2025-38710</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;gfs2: Validate i_depth for exhash directories&lt;/p&gt;
&lt;p&gt;A fuzzer test introduced corruption that ends up with a depth of 0 in
dir_e_read(), causing an undefined shift by 32 at:&lt;/p&gt;
&lt;p&gt;index = hash &amp;gt;&amp;gt; (32 - dip-&amp;gt;i_depth);&lt;/p&gt;
&lt;p&gt;As calculated in an open-coded way in dir_make_exhash(), the minimum
depth for an exhash directory is ilog2(sdp-&amp;gt;sd_hash_ptrs) and 0 is
invalid as sdp-&amp;gt;sd_hash_ptrs is fixed as sdp-&amp;gt;bsize / 16 at mount time.&lt;/p&gt;
&lt;p&gt;So we can avoid the undefined behaviour by checking for depth values
lower than the minimum in gfs2_dinode_in(). Values greater than the
maximum are already being checked for there.&lt;/p&gt;
&lt;p&gt;Also switch the calculation in dir_make_exhash() to use ilog2() to
clarify how the depth is calculated.&lt;/p&gt;
&lt;p&gt;Tested with the syzkaller repro.c and xfstests &amp;#39;-g quick&amp;#39;.&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;gfs2: Validate i_depth for exhash directories&lt;/p&gt;
&lt;p&gt;A fuzzer test introduced corruption that ends up with a depth of 0 in
dir_e_read(), causing an undefined shift by 32 at:&lt;/p&gt;
&lt;p&gt;index = hash &amp;gt;&amp;gt; (32 - dip-&amp;gt;i_depth);&lt;/p&gt;
&lt;p&gt;As calculated in an open-coded way in dir_make_exhash(), the minimum
depth for an exhash directory is ilog2(sdp-&amp;gt;sd_hash_ptrs) and 0 is
invalid as sdp-&amp;gt;sd_hash_ptrs is fixed as sdp-&amp;gt;bsize / 16 at mount time.&lt;/p&gt;
&lt;p&gt;So we can avoid the undefined behaviour by checking for depth values
lower than the minimum in gfs2_dinode_in(). Values greater than the
maximum are already being checked for there.&lt;/p&gt;
&lt;p&gt;Also switch the calculation in dir_make_exhash() to use ilog2() to
clarify how the depth is calculated.&lt;/p&gt;
&lt;p&gt;Tested with the syzkaller repro.c and xfstests &amp;#39;-g quick&amp;#39;.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2025-38710</guid>
    </item>
  </channel>
</rss>
