Vulnerability · Published May 8, 2026 · Assigned by Linux

CVE-2026-43309md raid: fix hang when stopping arrays with metadata through dm-raid

Medium 5.5

In plain English

A medium-severity security flaw in Linux from Linux. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 0.1% (higher than 2% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.

Severity (CVSS NVD)5.5Medium
Exploit odds (30 days)0.1%top 98.0% of all CVEs
Exploited in the wildNo reportsnot in CISA KEV
Attack toolingNoneno public tooling known

Official description

In the Linux kernel, the following vulnerability has been resolved: md raid: fix hang when stopping arrays with metadata through dm-raid When using device-mapper's dm-raid target, stopping a RAID array can cause the system to hang under specific conditions. This occurs when: - A dm-raid managed device tree is suspended from top to bottom (the top-level RAID device is suspended first, followed by its underlying metadata and data devices) - The top-level RAID device is then removed Removing the top-level device triggers a hang in the following sequence: the dm-raid destructor calls md_stop(), which tries to flush the write-intent bitmap by writing to the metadata sub-devices. However, these devices are already suspended, making them unable to complete the write-intent operations and causing an indefinite block. Fix: - Prevent bitmap flushing when md_stop() is called from dm-raid destructor context and avoid a quiescing/unquescing cycle which could also cause I/O - Still allow write-intent bitmap flushing when called from dm-raid suspend context This ensures that RAID array teardown can complete successfully even when the underlying devices are in a suspended state. This second patch uses md_is_rdwr() to distinguish between suspend and destructor paths as elaborated on above.

Affected packages & fixed versions

EcosystemPackageFixed inAdvisory
Debian:12linuxno fix listedDEBIAN-CVE-2026-43309
Debian:13linux6.12.115-2DEBIAN-CVE-2026-43309
Debian:14linux6.19.6-1DEBIAN-CVE-2026-43309
Ubuntu:22.04:LTSlinuxno fix listedUBUNTU-CVE-2026-43309
Ubuntu:24.04:LTSlinuxno fix listedUBUNTU-CVE-2026-43309
Ubuntu:25.10linuxno fix listedUBUNTU-CVE-2026-43309
Ubuntu:22.04:LTSlinux-allwinner-5.19no fix listedUBUNTU-CVE-2026-43309
Ubuntu:22.04:LTSlinux-awsno fix listedUBUNTU-CVE-2026-43309
Ubuntu:24.04:LTSlinux-awsno fix listedUBUNTU-CVE-2026-43309
Ubuntu:25.10linux-awsno fix listedUBUNTU-CVE-2026-43309
Ubuntu:22.04:LTSlinux-aws-5.19no fix listedUBUNTU-CVE-2026-43309
Ubuntu:24.04:LTSlinux-aws-6.14no fix listedUBUNTU-CVE-2026-43309
Ubuntu:24.04:LTSlinux-aws-6.17no fix listedUBUNTU-CVE-2026-43309
Ubuntu:22.04:LTSlinux-aws-6.2no fix listedUBUNTU-CVE-2026-43309
Ubuntu:22.04:LTSlinux-aws-6.5no fix listedUBUNTU-CVE-2026-43309
Ubuntu:22.04:LTSlinux-aws-6.8no fix listedUBUNTU-CVE-2026-43309
Ubuntu:22.04:LTSlinux-azureno fix listedUBUNTU-CVE-2026-43309
Ubuntu:24.04:LTSlinux-azureno fix listedUBUNTU-CVE-2026-43309
Ubuntu:25.10linux-azureno fix listedUBUNTU-CVE-2026-43309
Ubuntu:22.04:LTSlinux-azure-5.19no fix listedUBUNTU-CVE-2026-43309
Ubuntu:24.04:LTSlinux-azure-6.11no fix listedUBUNTU-CVE-2026-43309
Ubuntu:24.04:LTSlinux-azure-6.14no fix listedUBUNTU-CVE-2026-43309
Ubuntu:24.04:LTSlinux-azure-6.17no fix listedUBUNTU-CVE-2026-43309
Ubuntu:22.04:LTSlinux-azure-6.2no fix listedUBUNTU-CVE-2026-43309
Ubuntu:22.04:LTSlinux-azure-6.5no fix listedUBUNTU-CVE-2026-43309
Ubuntu:22.04:LTSlinux-azure-6.8no fix listedUBUNTU-CVE-2026-43309
Ubuntu:22.04:LTSlinux-azure-fdeno fix listedUBUNTU-CVE-2026-43309
Ubuntu:24.04:LTSlinux-azure-fdeno fix listedUBUNTU-CVE-2026-43309
Ubuntu:25.10linux-azure-fdeno fix listedUBUNTU-CVE-2026-43309
Ubuntu:22.04:LTSlinux-azure-fde-5.19no fix listedUBUNTU-CVE-2026-43309
Ubuntu:24.04:LTSlinux-azure-fde-6.14no fix listedUBUNTU-CVE-2026-43309
Ubuntu:24.04:LTSlinux-azure-fde-6.17no fix listedUBUNTU-CVE-2026-43309
Ubuntu:22.04:LTSlinux-azure-fde-6.2no fix listedUBUNTU-CVE-2026-43309
Ubuntu:22.04:LTSlinux-azure-fde-6.8no fix listedUBUNTU-CVE-2026-43309
Ubuntu:24.04:LTSlinux-azure-nvidiano fix listedUBUNTU-CVE-2026-43309
Ubuntu:24.04:LTSlinux-azure-nvidia-6.14no fix listedUBUNTU-CVE-2026-43309
Ubuntu:22.04:LTSlinux-gcpno fix listedUBUNTU-CVE-2026-43309
Ubuntu:24.04:LTSlinux-gcpno fix listedUBUNTU-CVE-2026-43309
Ubuntu:25.10linux-gcpno fix listedUBUNTU-CVE-2026-43309
Ubuntu:22.04:LTSlinux-gcp-5.19no fix listedUBUNTU-CVE-2026-43309
Ubuntu:24.04:LTSlinux-gcp-6.11no fix listedUBUNTU-CVE-2026-43309
Ubuntu:24.04:LTSlinux-gcp-6.14no fix listedUBUNTU-CVE-2026-43309
Ubuntu:24.04:LTSlinux-gcp-6.17no fix listedUBUNTU-CVE-2026-43309
Ubuntu:22.04:LTSlinux-gcp-6.2no fix listedUBUNTU-CVE-2026-43309
Ubuntu:22.04:LTSlinux-gcp-6.5no fix listedUBUNTU-CVE-2026-43309
Ubuntu:22.04:LTSlinux-gcp-6.8no fix listedUBUNTU-CVE-2026-43309
Ubuntu:22.04:LTSlinux-gkeno fix listedUBUNTU-CVE-2026-43309
Ubuntu:24.04:LTSlinux-gkeno fix listedUBUNTU-CVE-2026-43309
Ubuntu:22.04:LTSlinux-gkeopno fix listedUBUNTU-CVE-2026-43309
Ubuntu:24.04:LTSlinux-gkeopno fix listedUBUNTU-CVE-2026-43309
Ubuntu:22.04:LTSlinux-hwe-5.19no fix listedUBUNTU-CVE-2026-43309
Ubuntu:24.04:LTSlinux-hwe-6.11no fix listedUBUNTU-CVE-2026-43309
Ubuntu:24.04:LTSlinux-hwe-6.14no fix listedUBUNTU-CVE-2026-43309
Ubuntu:24.04:LTSlinux-hwe-6.17no fix listedUBUNTU-CVE-2026-43309
Ubuntu:22.04:LTSlinux-hwe-6.2no fix listedUBUNTU-CVE-2026-43309
Ubuntu:22.04:LTSlinux-hwe-6.5no fix listedUBUNTU-CVE-2026-43309
Ubuntu:22.04:LTSlinux-hwe-6.8no fix listedUBUNTU-CVE-2026-43309
Ubuntu:22.04:LTSlinux-ibmno fix listedUBUNTU-CVE-2026-43309
Ubuntu:24.04:LTSlinux-ibmno fix listedUBUNTU-CVE-2026-43309
Ubuntu:22.04:LTSlinux-ibm-6.8no fix listedUBUNTU-CVE-2026-43309
Ubuntu:22.04:LTSlinux-intel-iot-realtimeno fix listedUBUNTU-CVE-2026-43309
Ubuntu:22.04:LTSlinux-intel-iotgno fix listedUBUNTU-CVE-2026-43309
Ubuntu:22.04:LTSlinux-kvmno fix listedUBUNTU-CVE-2026-43309
Ubuntu:22.04:LTSlinux-lowlatencyno fix listedUBUNTU-CVE-2026-43309
Ubuntu:24.04:LTSlinux-lowlatencyno fix listedUBUNTU-CVE-2026-43309
Ubuntu:22.04:LTSlinux-lowlatency-hwe-5.19no fix listedUBUNTU-CVE-2026-43309
Ubuntu:24.04:LTSlinux-lowlatency-hwe-6.11no fix listedUBUNTU-CVE-2026-43309
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.2no fix listedUBUNTU-CVE-2026-43309
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.5no fix listedUBUNTU-CVE-2026-43309
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.8no fix listedUBUNTU-CVE-2026-43309
Ubuntu:22.04:LTSlinux-nvidiano fix listedUBUNTU-CVE-2026-43309
Ubuntu:24.04:LTSlinux-nvidiano fix listedUBUNTU-CVE-2026-43309
Ubuntu:24.04:LTSlinux-nvidia-6.11no fix listedUBUNTU-CVE-2026-43309
Ubuntu:24.04:LTSlinux-nvidia-6.17no fix listedUBUNTU-CVE-2026-43309
Ubuntu:22.04:LTSlinux-nvidia-6.2no fix listedUBUNTU-CVE-2026-43309
Ubuntu:22.04:LTSlinux-nvidia-6.5no fix listedUBUNTU-CVE-2026-43309
Ubuntu:22.04:LTSlinux-nvidia-6.8no fix listedUBUNTU-CVE-2026-43309
Ubuntu:24.04:LTSlinux-nvidia-lowlatencyno fix listedUBUNTU-CVE-2026-43309
Ubuntu:22.04:LTSlinux-nvidia-tegrano fix listedUBUNTU-CVE-2026-43309
Ubuntu:24.04:LTSlinux-nvidia-tegrano fix listedUBUNTU-CVE-2026-43309
Ubuntu:22.04:LTSlinux-nvidia-tegra-igxno fix listedUBUNTU-CVE-2026-43309
Ubuntu:22.04:LTSlinux-oem-5.17no fix listedUBUNTU-CVE-2026-43309
Ubuntu:22.04:LTSlinux-oem-6.0no fix listedUBUNTU-CVE-2026-43309
Ubuntu:22.04:LTSlinux-oem-6.1no fix listedUBUNTU-CVE-2026-43309
Ubuntu:24.04:LTSlinux-oem-6.11no fix listedUBUNTU-CVE-2026-43309
Ubuntu:24.04:LTSlinux-oem-6.14no fix listedUBUNTU-CVE-2026-43309
Ubuntu:24.04:LTSlinux-oem-6.17no fix listedUBUNTU-CVE-2026-43309
Ubuntu:22.04:LTSlinux-oem-6.5no fix listedUBUNTU-CVE-2026-43309
Ubuntu:24.04:LTSlinux-oem-6.8no fix listedUBUNTU-CVE-2026-43309
Ubuntu:22.04:LTSlinux-oracleno fix listedUBUNTU-CVE-2026-43309
Ubuntu:24.04:LTSlinux-oracleno fix listedUBUNTU-CVE-2026-43309
Ubuntu:25.10linux-oracleno fix listedUBUNTU-CVE-2026-43309
Ubuntu:24.04:LTSlinux-oracle-6.14no fix listedUBUNTU-CVE-2026-43309
Ubuntu:24.04:LTSlinux-oracle-6.17no fix listedUBUNTU-CVE-2026-43309
Ubuntu:22.04:LTSlinux-oracle-6.5no fix listedUBUNTU-CVE-2026-43309
Ubuntu:22.04:LTSlinux-oracle-6.8no fix listedUBUNTU-CVE-2026-43309
Ubuntu:22.04:LTSlinux-raspino fix listedUBUNTU-CVE-2026-43309
Ubuntu:24.04:LTSlinux-raspino fix listedUBUNTU-CVE-2026-43309
Ubuntu:25.10linux-raspino fix listedUBUNTU-CVE-2026-43309
Ubuntu:24.04:LTSlinux-raspi-realtimeno fix listedUBUNTU-CVE-2026-43309
Ubuntu:22.04:LTSlinux-realtimeno fix listedUBUNTU-CVE-2026-43309
Ubuntu:24.04:LTSlinux-realtimeno fix listedUBUNTU-CVE-2026-43309
Ubuntu:25.10linux-realtimeno fix listedUBUNTU-CVE-2026-43309
Ubuntu:22.04:LTSlinux-riscvno fix listedUBUNTU-CVE-2026-43309
Ubuntu:24.04:LTSlinux-riscvno fix listedUBUNTU-CVE-2026-43309
Ubuntu:25.10linux-riscvno fix listedUBUNTU-CVE-2026-43309
Ubuntu:22.04:LTSlinux-riscv-5.19no fix listedUBUNTU-CVE-2026-43309
Ubuntu:24.04:LTSlinux-riscv-6.14no fix listedUBUNTU-CVE-2026-43309
Ubuntu:24.04:LTSlinux-riscv-6.17no fix listedUBUNTU-CVE-2026-43309
Ubuntu:22.04:LTSlinux-riscv-6.5no fix listedUBUNTU-CVE-2026-43309
Ubuntu:22.04:LTSlinux-riscv-6.8no fix listedUBUNTU-CVE-2026-43309
Ubuntu:22.04:LTSlinux-starfive-5.19no fix listedUBUNTU-CVE-2026-43309
Ubuntu:22.04:LTSlinux-starfive-6.2no fix listedUBUNTU-CVE-2026-43309
Ubuntu:22.04:LTSlinux-starfive-6.5no fix listedUBUNTU-CVE-2026-43309
Ubuntu:24.04:LTSlinux-vmwareno fix listedUBUNTU-CVE-2026-43309
Ubuntu:24.04:LTSlinux-xilinxno fix listedUBUNTU-CVE-2026-43309
Ubuntu:22.04:LTSlinux-xilinx-zynqmpno fix listedUBUNTU-CVE-2026-43309

Affected products (as reported)

VendorProductVersions
Linux Linux 0dd84b319352bb8ba64752d4e45396d8b13e6018 – before 63054027d95200b04f3cf624faa7817e0555d56a0dd84b319352bb8ba64752d4e45396d8b13e6018 – before 24783dd06de870d646c25207bae186f78195f9120dd84b319352bb8ba64752d4e45396d8b13e6018 – before 338378dfffbdbb8d37a18f0a0c0358812671f91e0dd84b319352bb8ba64752d4e45396d8b13e6018 – before cefcb9297fbdb6d94b61787b4f8d84f55b7414701678ca35b80a94d474fdc31e2497ce5d7ed52512690b5c90fd2d81fd1d2b6110fa36783232f6dce28e7fb19f1a744fd34e982633ced756fee0498ef7a5a58fab556bfe618b4c9719eb85712d78c6cb10
Linux Linux 6.0

References