Skip to main content
VulnerabilityPublished Updated

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

Affects Linux kernelSource CVE Database V5

0

Not known to be exploited · fixed in cefcb9297fbdb6d94b61787b4f8d84f55b741470 : update Linux kernel when convenient.

Data as of 26 Oct 2026, 14:18 UTC

Severity
Unrated

Rated by Threat Radar · No CVSS score from NVD or the CNA

EPSS
0.1% chance of exploitation in 30 days – higher than 1% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in cefcb9297fbdb6d94b61787b4f8d84f55b741470, 63054027d95200b04f3cf624faa7817e0555d56a, 338378dfffbdbb8d37a18f0a0c0358812671f91e +7

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 8 May 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • >=4.14.292 <4.15
  • >=4.19.257 <4.20
  • >=5.4.212 <5.5
  • >=5.10.140 <5.11
  • >=5.15.64 <5.16
  • >=5.19.6 <5.20
Fixed in
  • cefcb9297fbdb6d94b61787b4f8d84f55b741470
  • 63054027d95200b04f3cf624faa7817e0555d56a
  • 338378dfffbdbb8d37a18f0a0c0358812671f91e
  • 24783dd06de870d646c25207bae186f78195f912
  • 5.20
  • 5.16
  • 5.11
  • 5.5
  • 4.20
  • 4.15
LinuxLinuxAffected
  • =6.0
Fixed in–

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.

References

Community reviews

Loading reviews…