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.
Published: 2026-05-08
Score: n/a
EPSS: n/a
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

The vulnerability resides in the Linux kernel’s device‑mapper dm‑raid target. When a dm‑raid array that has metadata devices suspended is removed, the dm‑raid destructor calls md_stop(), which attempts to flush the write‑intent bitmap by writing to the suspended metadata sub‑devices. Because those devices cannot complete I/O while suspended, the flush operation blocks indefinitely, causing the kernel to hang and the system to become unresponsive. The flaw results in a local denial of service that affects overall system availability.

Affected Systems

Any Linux kernel build that includes the device‑mapper dm‑raid target and uses dm‑raid managed arrays with metadata devices is affected. The issue manifests when the array is torn down while its underlying metadata and data devices are in a suspended state. No specific kernel version is enumerated, so all versions that satisfy these conditions should be considered vulnerable until a patch is applied.

Risk and Exploitability

The CVSS score is not provided and the EPSS value is not available, but the vulnerability is not listed in CISA’s KEV catalog. The attack requires understanding of dm‑raid array management and the ability to trigger the teardown sequence, which typically implies root or privileged access to the system. Consequently, the risk is local only and limited to systems that use dm‑raid under conditions that allow the described suspend and removal sequence. Proper kernel updates or configuration changes mitigate the risk.

Generated by OpenCVE AI on May 8, 2026 at 15:10 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Apply a kernel update that includes the patch committing the prevention of bitmap flushing in dm‑raid destructor context (refer to the Git commits linked in the advisory).
  • If an immediate kernel update is not possible, avoid removing or stopping top‑level dm‑raid devices while their underlying metadata devices are suspended; ensure the metadata devices remain active during array teardown.
  • Alternatively, configure the system to prevent suspension of the metadata devices while dm‑raid arrays are operational, thereby avoiding the problematic state that triggers the hang.

Generated by OpenCVE AI on May 8, 2026 at 15:10 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Fri, 08 May 2026 15:30:00 +0000

Type Values Removed Values Added
Weaknesses CWE-362
CWE-917

Fri, 08 May 2026 13:30:00 +0000

Type Values Removed Values Added
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.
Title md raid: fix hang when stopping arrays with metadata through dm-raid
First Time appeared Linux
Linux linux Kernel
CPEs cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
Vendors & Products Linux
Linux linux Kernel
References

Subscriptions

Linux Linux Kernel
cve-icon MITRE

Status: PUBLISHED

Assigner: Linux

Published:

Updated: 2026-05-08T13:11:27.595Z

Reserved: 2026-05-01T14:12:56.000Z

Link: CVE-2026-43309

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Received

Published: 2026-05-08T14:16:38.250

Modified: 2026-05-08T14:16:38.250

Link: CVE-2026-43309

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-05-08T16:15:12Z

Weaknesses