<?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 15:31:55 +0000</lastBuildDate>
    <item>
      <title>CVE-2025-22036 — exfat: fix random stack corruption after get_block</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2025-22036</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;exfat: fix random stack corruption after get_block&lt;/p&gt;
&lt;p&gt;When get_block is called with a buffer_head allocated on the stack, such
as do_mpage_readpage, stack corruption due to buffer_head UAF may occur in
the following race condition situation.&lt;/p&gt;
&lt;p&gt;&amp;lt;CPU 0&amp;gt;                      &amp;lt;CPU 1&amp;gt;
mpage_read_folio
  &amp;lt;&amp;lt;bh on stack&amp;gt;&amp;gt;
  do_mpage_readpage
    exfat_get_block
      bh_read
        __bh_read
	  get_bh(bh)
          submit_bh
          wait_on_buffer
                              ...
                              end_buffer_read_sync
                                __end_buffer_read_notouch
                                   unlock_buffer
          &amp;lt;&amp;lt;keep going&amp;gt;&amp;gt;
        ...
      ...
    ...
  ...
&amp;lt;&amp;lt;bh is not valid out of mpage_read_folio&amp;gt;&amp;gt;
   .
   .
another_function
  &amp;lt;&amp;lt;variable A on stack&amp;gt;&amp;gt;
                                   put_bh(bh)
                                     atomic_dec(bh-&amp;gt;b_count)
  * stack corruption here *&lt;/p&gt;
&lt;p&gt;This patch returns -EAGAIN if a folio does not have buffers when bh_read
needs to be called. By doing this, the caller can fallback to functions
like block_read_full_folio(), create a buffer_head in the folio, and then
call get_block again.&lt;/p&gt;
&lt;p&gt;Let&amp;#39;s do not call bh_read() with on-stack buffer_head.&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;exfat: fix random stack corruption after get_block&lt;/p&gt;
&lt;p&gt;When get_block is called with a buffer_head allocated on the stack, such
as do_mpage_readpage, stack corruption due to buffer_head UAF may occur in
the following race condition situation.&lt;/p&gt;
&lt;p&gt;&amp;lt;CPU 0&amp;gt;                      &amp;lt;CPU 1&amp;gt;
mpage_read_folio
  &amp;lt;&amp;lt;bh on stack&amp;gt;&amp;gt;
  do_mpage_readpage
    exfat_get_block
      bh_read
        __bh_read
	  get_bh(bh)
          submit_bh
          wait_on_buffer
                              ...
                              end_buffer_read_sync
                                __end_buffer_read_notouch
                                   unlock_buffer
          &amp;lt;&amp;lt;keep going&amp;gt;&amp;gt;
        ...
      ...
    ...
  ...
&amp;lt;&amp;lt;bh is not valid out of mpage_read_folio&amp;gt;&amp;gt;
   .
   .
another_function
  &amp;lt;&amp;lt;variable A on stack&amp;gt;&amp;gt;
                                   put_bh(bh)
                                     atomic_dec(bh-&amp;gt;b_count)
  * stack corruption here *&lt;/p&gt;
&lt;p&gt;This patch returns -EAGAIN if a folio does not have buffers when bh_read
needs to be called. By doing this, the caller can fallback to functions
like block_read_full_folio(), create a buffer_head in the folio, and then
call get_block again.&lt;/p&gt;
&lt;p&gt;Let&amp;#39;s do not call bh_read() with on-stack buffer_head.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2025-22036</guid>
    </item>
  </channel>
</rss>
