<?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>Fri, 02 Oct 2026 03:56:28 +0000</lastBuildDate>
    <item>
      <title>CVE-2023-53832 — md/raid10: fix null-ptr-deref in raid10_sync_request</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2023-53832</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/raid10: fix null-ptr-deref in raid10_sync_request&lt;/p&gt;
&lt;p&gt;init_resync() inits mempool and sets conf-&amp;gt;have_replacemnt at the beginning
of sync, close_sync() frees the mempool when sync is completed.&lt;/p&gt;
&lt;p&gt;After [1] recovery might be skipped and init_resync() is called but
close_sync() is not. null-ptr-deref occurs with r10bio-&amp;gt;dev[i].repl_bio.&lt;/p&gt;
&lt;p&gt;The following is one way to reproduce the issue.&lt;/p&gt;
&lt;p&gt;1) create a array, wait for resync to complete, mddev-&amp;gt;recovery_cp is set
     to MaxSector.
  2) recovery is woken and it is skipped. conf-&amp;gt;have_replacement is set to
     0 in init_resync(). close_sync() not called.
  3) some io errors and rdev A is set to WantReplacement.
  4) a new device is added and set to A&amp;#39;s replacement.
  5) recovery is woken, A have replacement, but conf-&amp;gt;have_replacemnt is
     0. r10bio-&amp;gt;dev[i].repl_bio will not be alloced and null-ptr-deref
     occurs.&lt;/p&gt;
&lt;p&gt;Fix it by not calling init_resync() if recovery skipped.&lt;/p&gt;
&lt;p&gt;[1] commit 7e83ccbecd60 (&amp;#34;md/raid10: Allow skipping recovery when clean arrays are assembled&amp;#34;)&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/raid10: fix null-ptr-deref in raid10_sync_request&lt;/p&gt;
&lt;p&gt;init_resync() inits mempool and sets conf-&amp;gt;have_replacemnt at the beginning
of sync, close_sync() frees the mempool when sync is completed.&lt;/p&gt;
&lt;p&gt;After [1] recovery might be skipped and init_resync() is called but
close_sync() is not. null-ptr-deref occurs with r10bio-&amp;gt;dev[i].repl_bio.&lt;/p&gt;
&lt;p&gt;The following is one way to reproduce the issue.&lt;/p&gt;
&lt;p&gt;1) create a array, wait for resync to complete, mddev-&amp;gt;recovery_cp is set
     to MaxSector.
  2) recovery is woken and it is skipped. conf-&amp;gt;have_replacement is set to
     0 in init_resync(). close_sync() not called.
  3) some io errors and rdev A is set to WantReplacement.
  4) a new device is added and set to A&amp;#39;s replacement.
  5) recovery is woken, A have replacement, but conf-&amp;gt;have_replacemnt is
     0. r10bio-&amp;gt;dev[i].repl_bio will not be alloced and null-ptr-deref
     occurs.&lt;/p&gt;
&lt;p&gt;Fix it by not calling init_resync() if recovery skipped.&lt;/p&gt;
&lt;p&gt;[1] commit 7e83ccbecd60 (&amp;#34;md/raid10: Allow skipping recovery when clean arrays are assembled&amp;#34;)&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2023-53832</guid>
    </item>
  </channel>
</rss>
