<?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>Mon, 05 Oct 2026 10:57:25 +0000</lastBuildDate>
    <item>
      <title>CVE-2024-26755 — md: Don't suspend the array for interrupted reshape</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2024-26755</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: Don&amp;#39;t suspend the array for interrupted reshape&lt;/p&gt;
&lt;p&gt;md_start_sync() will suspend the array if there are spares that can be
added or removed from conf, however, if reshape is still in progress,
this won&amp;#39;t happen at all or data will be corrupted(remove_and_add_spares
won&amp;#39;t be called from md_choose_sync_action for reshape), hence there is
no need to suspend the array if reshape is not done yet.&lt;/p&gt;
&lt;p&gt;Meanwhile, there is a potential deadlock for raid456:&lt;/p&gt;
&lt;p&gt;1) reshape is interrupted;&lt;/p&gt;
&lt;p&gt;2) set one of the disk WantReplacement, and add a new disk to the array,
   however, recovery won&amp;#39;t start until the reshape is finished;&lt;/p&gt;
&lt;p&gt;3) then issue an IO across reshpae position, this IO will wait for
   reshape to make progress;&lt;/p&gt;
&lt;p&gt;4) continue to reshape, then md_start_sync() found there is a spare disk
   that can be added to conf, mddev_suspend() is called;&lt;/p&gt;
&lt;p&gt;Step 4 and step 3 is waiting for each other, deadlock triggered. Noted
this problem is found by code review, and it&amp;#39;s not reporduced yet.&lt;/p&gt;
&lt;p&gt;Fix this porblem by don&amp;#39;t suspend the array for interrupted reshape,
this is safe because conf won&amp;#39;t be changed until reshape is done.&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: Don&amp;#39;t suspend the array for interrupted reshape&lt;/p&gt;
&lt;p&gt;md_start_sync() will suspend the array if there are spares that can be
added or removed from conf, however, if reshape is still in progress,
this won&amp;#39;t happen at all or data will be corrupted(remove_and_add_spares
won&amp;#39;t be called from md_choose_sync_action for reshape), hence there is
no need to suspend the array if reshape is not done yet.&lt;/p&gt;
&lt;p&gt;Meanwhile, there is a potential deadlock for raid456:&lt;/p&gt;
&lt;p&gt;1) reshape is interrupted;&lt;/p&gt;
&lt;p&gt;2) set one of the disk WantReplacement, and add a new disk to the array,
   however, recovery won&amp;#39;t start until the reshape is finished;&lt;/p&gt;
&lt;p&gt;3) then issue an IO across reshpae position, this IO will wait for
   reshape to make progress;&lt;/p&gt;
&lt;p&gt;4) continue to reshape, then md_start_sync() found there is a spare disk
   that can be added to conf, mddev_suspend() is called;&lt;/p&gt;
&lt;p&gt;Step 4 and step 3 is waiting for each other, deadlock triggered. Noted
this problem is found by code review, and it&amp;#39;s not reporduced yet.&lt;/p&gt;
&lt;p&gt;Fix this porblem by don&amp;#39;t suspend the array for interrupted reshape,
this is safe because conf won&amp;#39;t be changed until reshape is done.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2024-26755</guid>
    </item>
  </channel>
</rss>
