CVE-2026-43309

MEDIUMNVD 5.55.5—
EchelonGraph scoreMEDIUM confidence

Score 5.5 from GitHub Security Advisory published 2026-05-08. NVD baseline CVSS 5.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
5.5
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 5.5Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
5.5
EG Score
5.5(medium)
EPSS
2.2%
KEV
Not listed

Published

May 8, 2026

Last Modified

May 15, 2026

Advisory Details (3)

Auto-updated Jun 15, 2026
No patch confirmed yet.
generic

md raid: fix hang when stopping arrays with metadata through dm-raid - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/cefcb9297fbdb6d94b61787b4f8d84f55b741470
generic

md raid: fix hang when stopping arrays with metadata through dm-raid - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/338378dfffbdbb8d37a18f0a0c0358812671f91e
generic

md raid: fix hang when stopping arrays with metadata through dm-raid - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/24783dd06de870d646c25207bae186f78195f912

Vendor Advisories for CVE-2026-43309(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Data Freshness Timeline

(refreshed 7× in last 7d / 39× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 107 total refreshes for this CVE.

  1. 2026-07-15 16:57 UTCEPSS rescore
  2. 2026-07-15 02:00 UTCEPSS rescore
  3. 2026-07-13 22:30 UTCEPSS rescore
  4. 2026-07-13 06:13 UTCEPSS rescore
  5. 2026-07-12 05:46 UTCEPSS rescore
  6. 2026-07-11 08:27 UTCEPSS rescore
  7. 2026-07-09 19:10 UTCEPSS rescore
  8. 2026-07-08 15:16 UTCEPSS rescore
  9. 2026-07-07 13:46 UTCEPSS rescore
  10. 2026-07-06 16:27 UTCEPSS rescore
  11. 2026-07-06 02:23 UTCEPSS rescore
  12. 2026-07-05 02:30 UTCEPSS rescore
  13. 2026-07-04 06:31 UTCEPSS rescore
  14. 2026-07-01 15:06 UTCEPSS rescore
  15. 2026-06-30 23:22 UTCEPSS rescore
  16. 2026-06-29 14:06 UTCEPSS rescore
  17. 2026-06-28 14:07 UTCEPSS rescore
  18. 2026-06-28 05:09 UTCEG score recompute
  19. 2026-06-28 05:09 UTCGHSA enrichment
  20. 2026-06-28 04:56 UTCEPSS rescore
  21. 2026-06-27 03:08 UTCEPSS rescore
  22. 2026-06-26 21:36 UTCEG score recompute
  23. 2026-06-26 21:36 UTCGHSA enrichment
  24. 2026-06-25 13:49 UTCEPSS rescore
  25. 2026-06-25 13:49 UTCEPSS rescore
Show 75 more
  1. 2026-06-24 14:05 UTCEPSS rescore
  2. 2026-06-23 21:33 UTCEPSS rescore
  3. 2026-06-22 14:25 UTCEPSS rescore
  4. 2026-06-22 14:25 UTCEPSS rescore
  5. 2026-06-21 14:56 UTCEPSS rescore
  6. 2026-06-21 14:56 UTCEPSS rescore
  7. 2026-06-21 01:59 UTCEPSS rescore
  8. 2026-06-19 19:25 UTCEPSS rescore
  9. 2026-06-18 17:52 UTCEPSS rescore
  10. 2026-06-18 17:52 UTCEPSS rescore
  11. 2026-06-17 17:53 UTCEPSS rescore
  12. 2026-06-17 02:00 UTCEG score recompute
  13. 2026-06-17 02:00 UTCGHSA enrichment
  14. 2026-06-16 17:52 UTCEPSS rescore
  15. 2026-06-15 17:49 UTCEPSS rescore
  16. 2026-06-15 02:44 UTCEG score recompute
  17. 2026-06-15 02:43 UTCGHSA enrichment
  18. 2026-06-14 03:00 UTCEG score recompute
  19. 2026-06-14 02:59 UTCGHSA enrichment
  20. 2026-06-13 23:00 UTCEPSS rescore
  21. 2026-06-12 23:12 UTCEPSS rescore
  22. 2026-06-12 23:12 UTCEPSS rescore
  23. 2026-06-12 05:09 UTCEG score recompute
  24. 2026-06-12 05:09 UTCGHSA enrichment
  25. 2026-06-11 14:00 UTCEPSS rescore
  26. 2026-06-11 05:25 UTCEG score recompute
  27. 2026-06-11 05:25 UTCGHSA enrichment
  28. 2026-06-10 22:18 UTCEPSS rescore
  29. 2026-06-10 13:22 UTCEPSS rescore
  30. 2026-06-10 13:22 UTCEPSS rescore
  31. 2026-06-10 05:41 UTCEG score recompute
  32. 2026-06-10 05:41 UTCGHSA enrichment
  33. 2026-06-09 05:58 UTCEG score recompute
  34. 2026-06-09 05:58 UTCGHSA enrichment
  35. 2026-06-08 14:17 UTCEPSS rescore
  36. 2026-06-08 14:17 UTCEPSS rescore
  37. 2026-06-08 06:13 UTCEG score recompute
  38. 2026-06-08 06:13 UTCGHSA enrichment
  39. 2026-06-07 15:25 UTCEPSS rescore
  40. 2026-06-07 15:25 UTCEPSS rescore
  41. 2026-06-07 06:30 UTCEG score recompute
  42. 2026-06-07 06:30 UTCGHSA enrichment
  43. 2026-06-06 13:47 UTCEPSS rescore
  44. 2026-06-06 13:47 UTCEPSS rescore
  45. 2026-06-06 06:46 UTCEG score recompute
  46. 2026-06-06 06:46 UTCGHSA enrichment
  47. 2026-06-05 22:47 UTCEPSS rescore
  48. 2026-06-05 07:02 UTCEG score recompute
  49. 2026-06-05 07:02 UTCGHSA enrichment
  50. 2026-06-05 06:10 UTCEPSS rescore
  51. 2026-06-05 06:10 UTCEPSS rescore
  52. 2026-06-04 13:12 UTCEPSS rescore
  53. 2026-06-04 13:12 UTCEPSS rescore
  54. 2026-06-04 07:18 UTCEG score recompute
  55. 2026-06-04 07:18 UTCGHSA enrichment
  56. 2026-06-03 07:34 UTCEG score recompute
  57. 2026-06-03 07:34 UTCGHSA enrichment
  58. 2026-06-02 20:13 UTCEPSS rescore
  59. 2026-06-02 07:50 UTCEG score recompute
  60. 2026-06-02 07:50 UTCGHSA enrichment
  61. 2026-06-01 13:52 UTCEPSS rescore
  62. 2026-06-01 13:52 UTCEPSS rescore
  63. 2026-06-01 08:05 UTCEG score recompute
  64. 2026-06-01 08:05 UTCGHSA enrichment
  65. 2026-05-31 22:30 UTCEPSS rescore
  66. 2026-05-31 22:30 UTCEPSS rescore
  67. 2026-05-31 00:16 UTCEPSS rescore
  68. 2026-05-31 00:16 UTCEPSS rescore
  69. 2026-05-29 13:44 UTCEPSS rescore
  70. 2026-05-29 13:44 UTCEPSS rescore
  71. 2026-05-28 13:44 UTCEPSS rescore
  72. 2026-05-28 13:44 UTCEPSS rescore
  73. 2026-05-27 13:40 UTCEPSS rescore
  74. 2026-05-27 13:40 UTCEPSS rescore
  75. 2026-05-26 13:44 UTCEPSS rescore

Frequently asked(5)

What is CVE-2026-43309?
CVE-2026-43309 is a medium vulnerability published on May 8, 2026. 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…
When was CVE-2026-43309 disclosed?
CVE-2026-43309 was first published in the National Vulnerability Database on May 8, 2026, with the most recent update on May 15, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-43309 actively exploited?
CVE-2026-43309 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 2.2% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-43309?
CVE-2026-43309 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-43309?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-43309, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-43309

Explore →

Is Your Infrastructure Affected by CVE-2026-43309?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs