<?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, 28 Sep 2026 09:33:16 +0000</lastBuildDate>
    <item>
      <title>CVE-2025-71135 — md/raid5: fix possible null-pointer dereferences in raid5_store_group_thread_cnt()</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2025-71135</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/raid5: fix possible null-pointer dereferences in raid5_store_group_thread_cnt()&lt;/p&gt;
&lt;p&gt;The variable mddev-&amp;gt;private is first assigned to conf and then checked:&lt;/p&gt;
&lt;p&gt;conf = mddev-&amp;gt;private;
  if (!conf) ...&lt;/p&gt;
&lt;p&gt;If conf is NULL, then mddev-&amp;gt;private is also NULL. In this case,
null-pointer dereferences can occur when calling raid5_quiesce():&lt;/p&gt;
&lt;p&gt;raid5_quiesce(mddev, true);
  raid5_quiesce(mddev, false);&lt;/p&gt;
&lt;p&gt;since mddev-&amp;gt;private is assigned to conf again in raid5_quiesce(), and conf
is dereferenced in several places, for example:&lt;/p&gt;
&lt;p&gt;conf-&amp;gt;quiesce = 0;
  wake_up(&amp;amp;conf-&amp;gt;wait_for_quiescent);&lt;/p&gt;
&lt;p&gt;To fix this issue, the function should unlock mddev and return before
invoking raid5_quiesce() when conf is NULL, following the existing pattern
in raid5_change_consistency_policy().&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/raid5: fix possible null-pointer dereferences in raid5_store_group_thread_cnt()&lt;/p&gt;
&lt;p&gt;The variable mddev-&amp;gt;private is first assigned to conf and then checked:&lt;/p&gt;
&lt;p&gt;conf = mddev-&amp;gt;private;
  if (!conf) ...&lt;/p&gt;
&lt;p&gt;If conf is NULL, then mddev-&amp;gt;private is also NULL. In this case,
null-pointer dereferences can occur when calling raid5_quiesce():&lt;/p&gt;
&lt;p&gt;raid5_quiesce(mddev, true);
  raid5_quiesce(mddev, false);&lt;/p&gt;
&lt;p&gt;since mddev-&amp;gt;private is assigned to conf again in raid5_quiesce(), and conf
is dereferenced in several places, for example:&lt;/p&gt;
&lt;p&gt;conf-&amp;gt;quiesce = 0;
  wake_up(&amp;amp;conf-&amp;gt;wait_for_quiescent);&lt;/p&gt;
&lt;p&gt;To fix this issue, the function should unlock mddev and return before
invoking raid5_quiesce() when conf is NULL, following the existing pattern
in raid5_change_consistency_policy().&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2025-71135</guid>
    </item>
  </channel>
</rss>
