<?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 18:57:43 +0000</lastBuildDate>
    <item>
      <title>CVE-2024-43820 — dm-raid: Fix WARN_ON_ONCE check for sync_thread in raid_resume</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2024-43820</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;dm-raid: Fix WARN_ON_ONCE check for sync_thread in raid_resume&lt;/p&gt;
&lt;p&gt;rm-raid devices will occasionally trigger the following warning when
being resumed after a table load because DM_RECOVERY_RUNNING is set:&lt;/p&gt;
&lt;p&gt;WARNING: CPU: 7 PID: 5660 at drivers/md/dm-raid.c:4105 raid_resume+0xee/0x100 [dm_raid]&lt;/p&gt;
&lt;p&gt;The failing check is:
WARN_ON_ONCE(test_bit(MD_RECOVERY_RUNNING, &amp;amp;mddev-&amp;gt;recovery));&lt;/p&gt;
&lt;p&gt;This check is designed to make sure that the sync thread isn&amp;#39;t
registered, but md_check_recovery can set MD_RECOVERY_RUNNING without
the sync_thread ever getting registered. Instead of checking if
MD_RECOVERY_RUNNING is set, check if sync_thread is non-NULL.&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;dm-raid: Fix WARN_ON_ONCE check for sync_thread in raid_resume&lt;/p&gt;
&lt;p&gt;rm-raid devices will occasionally trigger the following warning when
being resumed after a table load because DM_RECOVERY_RUNNING is set:&lt;/p&gt;
&lt;p&gt;WARNING: CPU: 7 PID: 5660 at drivers/md/dm-raid.c:4105 raid_resume+0xee/0x100 [dm_raid]&lt;/p&gt;
&lt;p&gt;The failing check is:
WARN_ON_ONCE(test_bit(MD_RECOVERY_RUNNING, &amp;amp;mddev-&amp;gt;recovery));&lt;/p&gt;
&lt;p&gt;This check is designed to make sure that the sync thread isn&amp;#39;t
registered, but md_check_recovery can set MD_RECOVERY_RUNNING without
the sync_thread ever getting registered. Instead of checking if
MD_RECOVERY_RUNNING is set, check if sync_thread is non-NULL.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2024-43820</guid>
    </item>
  </channel>
</rss>
