{"api_version":"1","generated_at":"2026-05-13T07:41:00+00:00","cve":"CVE-2026-43309","urls":{"html":"https://cve.report/CVE-2026-43309","api":"https://cve.report/api/cve/CVE-2026-43309.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2026-43309","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2026-43309"},"summary":{"title":"md raid: fix hang when stopping arrays with metadata through dm-raid","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nmd raid: fix hang when stopping arrays with metadata through dm-raid\n\nWhen using device-mapper's dm-raid target, stopping a RAID array can cause\nthe system to hang under specific conditions.\n\nThis occurs when:\n\n- A dm-raid managed device tree is suspended from top to bottom\n   (the top-level RAID device is suspended first, followed by its\n    underlying metadata and data devices)\n\n- The top-level RAID device is then removed\n\nRemoving the top-level device triggers a hang in the following sequence:\nthe dm-raid destructor calls md_stop(), which tries to flush the\nwrite-intent bitmap by writing to the metadata sub-devices. However, these\ndevices are already suspended, making them unable to complete the write-intent\noperations and causing an indefinite block.\n\nFix:\n\n- Prevent bitmap flushing when md_stop() is called from dm-raid\ndestructor context\n  and avoid a quiescing/unquescing cycle which could also cause I/O\n\n- Still allow write-intent bitmap flushing when called from dm-raid\nsuspend context\n\nThis ensures that RAID array teardown can complete successfully even when the\nunderlying devices are in a suspended state.\n\nThis second patch uses md_is_rdwr() to distinguish between suspend and\ndestructor paths as elaborated on above.","state":"PUBLISHED","assigner":"Linux","published_at":"2026-05-08 14:16:38","updated_at":"2026-05-12 14:10:27"},"problem_types":[],"metrics":[],"references":[{"url":"https://git.kernel.org/stable/c/24783dd06de870d646c25207bae186f78195f912","name":"https://git.kernel.org/stable/c/24783dd06de870d646c25207bae186f78195f912","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/cefcb9297fbdb6d94b61787b4f8d84f55b741470","name":"https://git.kernel.org/stable/c/cefcb9297fbdb6d94b61787b4f8d84f55b741470","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/338378dfffbdbb8d37a18f0a0c0358812671f91e","name":"https://git.kernel.org/stable/c/338378dfffbdbb8d37a18f0a0c0358812671f91e","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-43309","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43309","name":"NVD vulnerability detail","refsource":"NVD","tags":["canonical","analysis"]}],"affected":[{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 0dd84b319352bb8ba64752d4e45396d8b13e6018 24783dd06de870d646c25207bae186f78195f912 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 0dd84b319352bb8ba64752d4e45396d8b13e6018 338378dfffbdbb8d37a18f0a0c0358812671f91e git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 0dd84b319352bb8ba64752d4e45396d8b13e6018 cefcb9297fbdb6d94b61787b4f8d84f55b741470 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 1678ca35b80a94d474fdc31e2497ce5d7ed52512 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 690b5c90fd2d81fd1d2b6110fa36783232f6dce2 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 8e7fb19f1a744fd34e982633ced756fee0498ef7 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected a5a58fab556bfe618b4c9719eb85712d78c6cb10 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 661c01b2181d9413c799127f13143583b69f20fd git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected f42a9819ba84bed2e609a4dff56af37063dcabdc git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 6.0","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.0 semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.18.16 6.18.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.19.6 6.19.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.0 * original_commit_for_fix","platforms":[]}],"timeline":[],"solutions":[],"workarounds":[],"exploits":[],"credits":[],"nvd_cpes":[],"vendor_comments":[],"enrichments":{"kev":null,"epss":{"cve_year":"2026","cve_id":"43309","cve":"CVE-2026-43309","epss":"0.000170000","percentile":"0.041320000","score_date":"2026-05-12","updated_at":"2026-05-13 00:11:53"},"legacy_qids":[]},"source_records":{"cve_program":{"containers":{"cna":{"affected":[{"defaultStatus":"unaffected","product":"Linux","programFiles":["drivers/md/md.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"lessThan":"24783dd06de870d646c25207bae186f78195f912","status":"affected","version":"0dd84b319352bb8ba64752d4e45396d8b13e6018","versionType":"git"},{"lessThan":"338378dfffbdbb8d37a18f0a0c0358812671f91e","status":"affected","version":"0dd84b319352bb8ba64752d4e45396d8b13e6018","versionType":"git"},{"lessThan":"cefcb9297fbdb6d94b61787b4f8d84f55b741470","status":"affected","version":"0dd84b319352bb8ba64752d4e45396d8b13e6018","versionType":"git"},{"status":"affected","version":"1678ca35b80a94d474fdc31e2497ce5d7ed52512","versionType":"git"},{"status":"affected","version":"690b5c90fd2d81fd1d2b6110fa36783232f6dce2","versionType":"git"},{"status":"affected","version":"8e7fb19f1a744fd34e982633ced756fee0498ef7","versionType":"git"},{"status":"affected","version":"a5a58fab556bfe618b4c9719eb85712d78c6cb10","versionType":"git"},{"status":"affected","version":"661c01b2181d9413c799127f13143583b69f20fd","versionType":"git"},{"status":"affected","version":"f42a9819ba84bed2e609a4dff56af37063dcabdc","versionType":"git"}]},{"defaultStatus":"affected","product":"Linux","programFiles":["drivers/md/md.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"status":"affected","version":"6.0"},{"lessThan":"6.0","status":"unaffected","version":"0","versionType":"semver"},{"lessThanOrEqual":"6.18.*","status":"unaffected","version":"6.18.16","versionType":"semver"},{"lessThanOrEqual":"6.19.*","status":"unaffected","version":"6.19.6","versionType":"semver"},{"lessThanOrEqual":"*","status":"unaffected","version":"7.0","versionType":"original_commit_for_fix"}]}],"cpeApplicability":[{"nodes":[{"cpeMatch":[{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"6.18.16","versionStartIncluding":"6.0","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"6.19.6","versionStartIncluding":"6.0","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.0","versionStartIncluding":"6.0","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionStartIncluding":"4.14.292","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionStartIncluding":"4.19.257","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionStartIncluding":"5.4.212","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionStartIncluding":"5.10.140","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionStartIncluding":"5.15.64","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionStartIncluding":"5.19.6","vulnerable":true}],"negate":false,"operator":"OR"}]}],"descriptions":[{"lang":"en","value":"In the Linux kernel, the following vulnerability has been resolved:\n\nmd raid: fix hang when stopping arrays with metadata through dm-raid\n\nWhen using device-mapper's dm-raid target, stopping a RAID array can cause\nthe system to hang under specific conditions.\n\nThis occurs when:\n\n- A dm-raid managed device tree is suspended from top to bottom\n   (the top-level RAID device is suspended first, followed by its\n    underlying metadata and data devices)\n\n- The top-level RAID device is then removed\n\nRemoving the top-level device triggers a hang in the following sequence:\nthe dm-raid destructor calls md_stop(), which tries to flush the\nwrite-intent bitmap by writing to the metadata sub-devices. However, these\ndevices are already suspended, making them unable to complete the write-intent\noperations and causing an indefinite block.\n\nFix:\n\n- Prevent bitmap flushing when md_stop() is called from dm-raid\ndestructor context\n  and avoid a quiescing/unquescing cycle which could also cause I/O\n\n- Still allow write-intent bitmap flushing when called from dm-raid\nsuspend context\n\nThis ensures that RAID array teardown can complete successfully even when the\nunderlying devices are in a suspended state.\n\nThis second patch uses md_is_rdwr() to distinguish between suspend and\ndestructor paths as elaborated on above."}],"providerMetadata":{"dateUpdated":"2026-05-11T22:22:04.039Z","orgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","shortName":"Linux"},"references":[{"url":"https://git.kernel.org/stable/c/24783dd06de870d646c25207bae186f78195f912"},{"url":"https://git.kernel.org/stable/c/338378dfffbdbb8d37a18f0a0c0358812671f91e"},{"url":"https://git.kernel.org/stable/c/cefcb9297fbdb6d94b61787b4f8d84f55b741470"}],"title":"md raid: fix hang when stopping arrays with metadata through dm-raid","x_generator":{"engine":"bippy-1.2.0"}}},"cveMetadata":{"assignerOrgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","assignerShortName":"Linux","cveId":"CVE-2026-43309","datePublished":"2026-05-08T13:11:27.595Z","dateReserved":"2026-05-01T14:12:56.000Z","dateUpdated":"2026-05-11T22:22:04.039Z","state":"PUBLISHED"},"dataType":"CVE_RECORD","dataVersion":"5.2"},"nvd":{"publishedDate":"2026-05-08 14:16:38","lastModifiedDate":"2026-05-12 14:10:27","problem_types":[],"metrics":[],"configurations":[]},"legacy_mitre":{"record":{"CveYear":"2026","CveId":"43309","Ordinal":"1","Title":"md raid: fix hang when stopping arrays with metadata through dm-","CVE":"CVE-2026-43309","Year":"2026"},"notes":[{"CveYear":"2026","CveId":"43309","Ordinal":"1","NoteData":"In the Linux kernel, the following vulnerability has been resolved:\n\nmd raid: fix hang when stopping arrays with metadata through dm-raid\n\nWhen using device-mapper's dm-raid target, stopping a RAID array can cause\nthe system to hang under specific conditions.\n\nThis occurs when:\n\n- A dm-raid managed device tree is suspended from top to bottom\n   (the top-level RAID device is suspended first, followed by its\n    underlying metadata and data devices)\n\n- The top-level RAID device is then removed\n\nRemoving the top-level device triggers a hang in the following sequence:\nthe dm-raid destructor calls md_stop(), which tries to flush the\nwrite-intent bitmap by writing to the metadata sub-devices. However, these\ndevices are already suspended, making them unable to complete the write-intent\noperations and causing an indefinite block.\n\nFix:\n\n- Prevent bitmap flushing when md_stop() is called from dm-raid\ndestructor context\n  and avoid a quiescing/unquescing cycle which could also cause I/O\n\n- Still allow write-intent bitmap flushing when called from dm-raid\nsuspend context\n\nThis ensures that RAID array teardown can complete successfully even when the\nunderlying devices are in a suspended state.\n\nThis second patch uses md_is_rdwr() to distinguish between suspend and\ndestructor paths as elaborated on above.","Type":"Description","Title":"md raid: fix hang when stopping arrays with metadata through dm-"}]}}}