<?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://db.gcve.eu</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>Wed, 30 Sep 2026 08:48:45 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-90400</title>
      <link>https://db.gcve.eu/vuln/fkie_cve-2026-90400</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;md: recheck spare changes before starting sync&lt;/p&gt;
&lt;p&gt;remove_spares() and remove_and_add_spares() modify the array&amp;#39;s rdev
configuration. These operations are only safe after the array has been
suspended.&lt;/p&gt;
&lt;p&gt;md_start_sync() checks whether spare configuration changes are needed
before taking reconfig_mutex. However, the rdev state can change before
the mutex is acquired, so the initial check can become stale. In that
case, md_choose_sync_action() may remove or replace rdevs while normal
I/O is still accessing them.&lt;/p&gt;
&lt;p&gt;The race can occur as follows:&lt;/p&gt;
&lt;p&gt;raid10d          Worker                      Normal IO
____________     _______________________     ______________________&lt;/p&gt;
&lt;p&gt;raid10_write_request()
                                             wait_blocked_dev()
set Blocked
set Faulty
                                             Skip Faulty rdev
                                             rrdev-&amp;gt;nr_pending++
                                             .repl_bio = bio
                 removeable_rdev = false     .
                 array not suspended         .
lock mddev                                   goto err_handle
                 lock mddev (wait)
                 .
update sb        .
clear Blocked    .
                 .
unlock mddev     .
                 lock mddev (acquires)
                 remove_spares()
                 removeable_rdev = true&lt;/p&gt;
&lt;p&gt;raid…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;md: recheck spare changes before starting sync&lt;/p&gt;
&lt;p&gt;remove_spares() and remove_and_add_spares() modify the array&amp;#39;s rdev
configuration. These operations are only safe after the array has been
suspended.&lt;/p&gt;
&lt;p&gt;md_start_sync() checks whether spare configuration changes are needed
before taking reconfig_mutex. However, the rdev state can change before
the mutex is acquired, so the initial check can become stale. In that
case, md_choose_sync_action() may remove or replace rdevs while normal
I/O is still accessing them.&lt;/p&gt;
&lt;p&gt;The race can occur as follows:&lt;/p&gt;
&lt;p&gt;raid10d          Worker                      Normal IO
____________     _______________________     ______________________&lt;/p&gt;
&lt;p&gt;raid10_write_request()
                                             wait_blocked_dev()
set Blocked
set Faulty
                                             Skip Faulty rdev
                                             rrdev-&amp;gt;nr_pending++
                                             .repl_bio = bio
                 removeable_rdev = false     .
                 array not suspended         .
lock mddev                                   goto err_handle
                 lock mddev (wait)
                 .
update sb        .
clear Blocked    .
                 .
unlock mddev     .
                 lock mddev (acquires)
                 remove_spares()
                 removeable_rdev = true&lt;/p&gt;
&lt;p&gt;raid…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/fkie_cve-2026-90400</guid>
    </item>
    <item>
      <title>GHSA-vwgq-hpcr-5x9r</title>
      <link>https://db.gcve.eu/vuln/ghsa-vwgq-hpcr-5x9r</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;md: recheck spare changes before starting sync&lt;/p&gt;
&lt;p&gt;remove_spares() and remove_and_add_spares() modify the array&amp;#39;s rdev
configuration. These operations are only safe after the array has been
suspended.&lt;/p&gt;
&lt;p&gt;md_start_sync() checks whether spare configuration changes are needed
before taking reconfig_mutex. However, the rdev state can change before
the mutex is acquired, so the initial check can become stale. In that
case, md_choose_sync_action() may remove or replace rdevs while normal
I/O is still accessing them.&lt;/p&gt;
&lt;p&gt;The race can occur as follows:&lt;/p&gt;
&lt;p&gt;raid10d          Worker                      Normal IO
____________     _______________________     ______________________&lt;/p&gt;
&lt;p&gt;raid10_write_request()
                                             wait_blocked_dev()
set Blocked
set Faulty
                                             Skip Faulty rdev
                                             rrdev-&amp;gt;nr_pending++
                                             .repl_bio = bio
                 removeable_rdev = false     .
                 array not suspended         .
lock mddev                                   goto err_handle
                 lock mddev (wait)
                 .
update sb        .
clear Blocked    .
                 .
unlock mddev     .
                 lock mddev (acquires)
                 remove_spares()
                 removeable_rdev = true&lt;/p&gt;
&lt;p&gt;raid…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;md: recheck spare changes before starting sync&lt;/p&gt;
&lt;p&gt;remove_spares() and remove_and_add_spares() modify the array&amp;#39;s rdev
configuration. These operations are only safe after the array has been
suspended.&lt;/p&gt;
&lt;p&gt;md_start_sync() checks whether spare configuration changes are needed
before taking reconfig_mutex. However, the rdev state can change before
the mutex is acquired, so the initial check can become stale. In that
case, md_choose_sync_action() may remove or replace rdevs while normal
I/O is still accessing them.&lt;/p&gt;
&lt;p&gt;The race can occur as follows:&lt;/p&gt;
&lt;p&gt;raid10d          Worker                      Normal IO
____________     _______________________     ______________________&lt;/p&gt;
&lt;p&gt;raid10_write_request()
                                             wait_blocked_dev()
set Blocked
set Faulty
                                             Skip Faulty rdev
                                             rrdev-&amp;gt;nr_pending++
                                             .repl_bio = bio
                 removeable_rdev = false     .
                 array not suspended         .
lock mddev                                   goto err_handle
                 lock mddev (wait)
                 .
update sb        .
clear Blocked    .
                 .
unlock mddev     .
                 lock mddev (acquires)
                 remove_spares()
                 removeable_rdev = true&lt;/p&gt;
&lt;p&gt;raid…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ghsa-vwgq-hpcr-5x9r</guid>
    </item>
    <item>
      <title>openSUSE-SU-2026:11893-1 — kernel-devel-7.2.8-1.1 on GA media</title>
      <link>https://db.gcve.eu/vuln/opensuse-su-2026:11893-1</link>
      <description>&lt;p&gt;kernel-devel-7.2.8-1.1 on GA media&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;kernel-devel-7.2.8-1.1 on GA media&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/opensuse-su-2026:11893-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-90400</title>
      <link>https://db.gcve.eu/vuln/ubuntu-cve-2026-90400</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3, Ubuntu:18.04:LTS: linux-gke-4.15, Ubuntu:18.04:LTS: linux-gke-5.4 and 154 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: md: recheck spare changes before starting sync remove_spares() and remove_and_add_spares() modify the array&amp;#39;s rdev configuration. These operations are only safe after the array has been suspended. md_start_sync() checks whether spare configuration changes are needed before taking reconfig_mutex. However, the rdev state can change before the mutex is acquired, so the initial check can become stale. In that case, md_choose_sync_action() may remove or replace rdevs while normal I/O is still accessing them. The race can occur as follows: raid10d          Worker                      Normal IO ____________     _______________________     ______________________                                              raid10_write_request()                                              wait_blocked_dev() set Blocked set Faulty                                              Skip Faulty rdev                                              rrdev-&amp;gt;nr_pending++                                              .repl_bio = bio                  removeable_rdev = false     .                  array not suspended         . lock mddev                                   goto err_handle                  lock mddev (wait)                  . update sb        . clear Blocked    .                  . unlock mddev     .                  lock mddev (acquires)                  remove_spares()                  removeable_rdev = true                  raid10_remo…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3, Ubuntu:18.04:LTS: linux-gke-4.15, Ubuntu:18.04:LTS: linux-gke-5.4 and 154 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: md: recheck spare changes before starting sync remove_spares() and remove_and_add_spares() modify the array&amp;#39;s rdev configuration. These operations are only safe after the array has been suspended. md_start_sync() checks whether spare configuration changes are needed before taking reconfig_mutex. However, the rdev state can change before the mutex is acquired, so the initial check can become stale. In that case, md_choose_sync_action() may remove or replace rdevs while normal I/O is still accessing them. The race can occur as follows: raid10d          Worker                      Normal IO ____________     _______________________     ______________________                                              raid10_write_request()                                              wait_blocked_dev() set Blocked set Faulty                                              Skip Faulty rdev                                              rrdev-&amp;gt;nr_pending++                                              .repl_bio = bio                  removeable_rdev = false     .                  array not suspended         . lock mddev                                   goto err_handle                  lock mddev (wait)                  . update sb        . clear Blocked    .                  . unlock mddev     .                  lock mddev (acquires)                  remove_spares()                  removeable_rdev = true                  raid10_remo…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ubuntu-cve-2026-90400</guid>
    </item>
  </channel>
</rss>
