Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

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

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.

Timeline

  1. ID reserved

    By Linux

  2. · 7 days later

    Published

  3. · 6 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2026-43309, by who scored it
Scored byCVSSScoreVector
NVDNVD · Modified3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.12% · top 98% of all CVEs (17 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.

Affected products

  • Linux · Linux

    • affected 0dd84b319352bb8ba64752d4e45396d8b13e6018 – < 63054027d95200b04f3cf624faa7817e0555d56a
    • affected 0dd84b319352bb8ba64752d4e45396d8b13e6018 – < 24783dd06de870d646c25207bae186f78195f912
    • affected 0dd84b319352bb8ba64752d4e45396d8b13e6018 – < 338378dfffbdbb8d37a18f0a0c0358812671f91e
    • affected 0dd84b319352bb8ba64752d4e45396d8b13e6018 – < cefcb9297fbdb6d94b61787b4f8d84f55b741470
    • affected 1678ca35b80a94d474fdc31e2497ce5d7ed52512
    • affected 690b5c90fd2d81fd1d2b6110fa36783232f6dce2
    • affected 8e7fb19f1a744fd34e982633ced756fee0498ef7
    • affected a5a58fab556bfe618b4c9719eb85712d78c6cb10
    • affected 661c01b2181d9413c799127f13143583b69f20fd
    • affected f42a9819ba84bed2e609a4dff56af37063dcabdc
    • affected 4.14.292 – < 4.15
    • affected 4.19.257 – < 4.20
    • affected 5.4.212 – < 5.5
    • affected 5.10.140 – < 5.11
    • affected 5.15.64 – < 5.16
    • affected 5.19.6 – < 5.20
  • Linux · Linux

    • affected 6.0
    • unaffected < 6.0
    • unaffected 6.12.114 – ≤ 6.12.*
    • unaffected 6.18.16 – ≤ 6.18.*
    • unaffected 6.19.6 – ≤ 6.19.*
    • unaffected 7.0 – ≤ *

References

References4

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-43309 badge
[![CVE-2026-43309](https://cveledger.app/badge/CVE-2026-43309.svg)](https://cveledger.app/cve/CVE-2026-43309)

Record last updated .