<?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>Thu, 01 Oct 2026 05:31:10 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-43271 — md-cluster: fix NULL pointer dereference in process_metadata_update</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-43271</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-cluster: fix NULL pointer dereference in process_metadata_update&lt;/p&gt;
&lt;p&gt;The function process_metadata_update() blindly dereferences the &amp;#39;thread&amp;#39;
pointer (acquired via rcu_dereference_protected) within the wait_event()
macro.&lt;/p&gt;
&lt;p&gt;While the code comment states &amp;#34;daemon thread must exist&amp;#34;, there is a valid
race condition window during the MD array startup sequence (md_run):&lt;/p&gt;
&lt;p&gt;1. bitmap_load() is called, which invokes md_cluster_ops-&amp;gt;join().
2. join() starts the &amp;#34;cluster_recv&amp;#34; thread (recv_daemon).
3. At this point, recv_daemon is active and processing messages.
4. However, mddev-&amp;gt;thread (the main MD thread) is not initialized until
   later in md_run().&lt;/p&gt;
&lt;p&gt;If a METADATA_UPDATED message is received from a remote node during this
specific window, process_metadata_update() will be called while
mddev-&amp;gt;thread is still NULL, leading to a kernel panic.&lt;/p&gt;
&lt;p&gt;To fix this, we must validate the &amp;#39;thread&amp;#39; pointer. If it is NULL, we
release the held lock (no_new_dev_lockres) and return early, safely
ignoring the update request as the array is not yet fully ready to
process it.&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-cluster: fix NULL pointer dereference in process_metadata_update&lt;/p&gt;
&lt;p&gt;The function process_metadata_update() blindly dereferences the &amp;#39;thread&amp;#39;
pointer (acquired via rcu_dereference_protected) within the wait_event()
macro.&lt;/p&gt;
&lt;p&gt;While the code comment states &amp;#34;daemon thread must exist&amp;#34;, there is a valid
race condition window during the MD array startup sequence (md_run):&lt;/p&gt;
&lt;p&gt;1. bitmap_load() is called, which invokes md_cluster_ops-&amp;gt;join().
2. join() starts the &amp;#34;cluster_recv&amp;#34; thread (recv_daemon).
3. At this point, recv_daemon is active and processing messages.
4. However, mddev-&amp;gt;thread (the main MD thread) is not initialized until
   later in md_run().&lt;/p&gt;
&lt;p&gt;If a METADATA_UPDATED message is received from a remote node during this
specific window, process_metadata_update() will be called while
mddev-&amp;gt;thread is still NULL, leading to a kernel panic.&lt;/p&gt;
&lt;p&gt;To fix this, we must validate the &amp;#39;thread&amp;#39; pointer. If it is NULL, we
release the held lock (no_new_dev_lockres) and return early, safely
ignoring the update request as the array is not yet fully ready to
process it.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-43271</guid>
    </item>
  </channel>
</rss>
