<?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 22:29:02 +0000</lastBuildDate>
    <item>
      <title>CVE-2025-38445 — md/raid1: Fix stack memory use after return in raid1_reshape</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2025-38445</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;md/raid1: Fix stack memory use after return in raid1_reshape&lt;/p&gt;
&lt;p&gt;In the raid1_reshape function, newpool is
allocated on the stack and assigned to conf-&amp;gt;r1bio_pool.
This results in conf-&amp;gt;r1bio_pool.wait.head pointing
to a stack address.
Accessing this address later can lead to a kernel panic.&lt;/p&gt;
&lt;p&gt;Example access path:&lt;/p&gt;
&lt;p&gt;raid1_reshape()
{
	// newpool is on the stack
	mempool_t newpool, oldpool;
	// initialize newpool.wait.head to stack address
	mempool_init(&amp;amp;newpool, ...);
	conf-&amp;gt;r1bio_pool = newpool;
}&lt;/p&gt;
&lt;p&gt;raid1_read_request() or raid1_write_request()
{
	alloc_r1bio()
	{
		mempool_alloc()
		{
			// if pool-&amp;gt;alloc fails
			remove_element()
			{
				--pool-&amp;gt;curr_nr;
			}
		}
	}
}&lt;/p&gt;
&lt;p&gt;mempool_free()
{
	if (pool-&amp;gt;curr_nr &amp;lt; pool-&amp;gt;min_nr) {
		// pool-&amp;gt;wait.head is a stack address
		// wake_up() will try to access this invalid address
		// which leads to a kernel panic
		return;
		wake_up(&amp;amp;pool-&amp;gt;wait);
	}
}&lt;/p&gt;
&lt;p&gt;Fix:
reinit conf-&amp;gt;r1bio_pool.wait after assigning newpool.&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;md/raid1: Fix stack memory use after return in raid1_reshape&lt;/p&gt;
&lt;p&gt;In the raid1_reshape function, newpool is
allocated on the stack and assigned to conf-&amp;gt;r1bio_pool.
This results in conf-&amp;gt;r1bio_pool.wait.head pointing
to a stack address.
Accessing this address later can lead to a kernel panic.&lt;/p&gt;
&lt;p&gt;Example access path:&lt;/p&gt;
&lt;p&gt;raid1_reshape()
{
	// newpool is on the stack
	mempool_t newpool, oldpool;
	// initialize newpool.wait.head to stack address
	mempool_init(&amp;amp;newpool, ...);
	conf-&amp;gt;r1bio_pool = newpool;
}&lt;/p&gt;
&lt;p&gt;raid1_read_request() or raid1_write_request()
{
	alloc_r1bio()
	{
		mempool_alloc()
		{
			// if pool-&amp;gt;alloc fails
			remove_element()
			{
				--pool-&amp;gt;curr_nr;
			}
		}
	}
}&lt;/p&gt;
&lt;p&gt;mempool_free()
{
	if (pool-&amp;gt;curr_nr &amp;lt; pool-&amp;gt;min_nr) {
		// pool-&amp;gt;wait.head is a stack address
		// wake_up() will try to access this invalid address
		// which leads to a kernel panic
		return;
		wake_up(&amp;amp;pool-&amp;gt;wait);
	}
}&lt;/p&gt;
&lt;p&gt;Fix:
reinit conf-&amp;gt;r1bio_pool.wait after assigning newpool.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2025-38445</guid>
    </item>
  </channel>
</rss>
