<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://vulnerability.circl.lu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-09-28T06:37:23.115215+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@circl.lu</email>
  </author>
  <link href="https://vulnerability.circl.lu" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/cve-2022-49987</id>
    <title>CVE-2022-49987 — md: call __md_stop_writes in md_stop</title>
    <updated>2026-09-28T06:37:23.130344+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Linux</p>
<p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>md: call __md_stop_writes in md_stop</p>
<p>From the link [1], we can see raid1d was running even after the path
raid_dtr -&gt; md_stop -&gt; __md_stop.</p>
<p>Let's stop write first in destructor to align with normal md-raid to
fix the KASAN issue.</p>
<p>[1]. https://lore.kernel.org/linux-raid/CAPhsuW5gc4AakdGNdF8ubpezAuDLFOYUO_sfMZcec6hQFm8nhg@mail.gmail.com/T/#m7f12bf90481c02c6d2da68c64aeed4779b7df74a</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2022-49987"/>
  </entry>
</feed>
