{
  "affected": [
    {
      "ecosystem_specific": {
        "urgency": "not yet assigned"
      },
      "package": {
        "ecosystem": "Debian:12",
        "name": "linux"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    },
    {
      "ecosystem_specific": {
        "urgency": "not yet assigned"
      },
      "package": {
        "ecosystem": "Debian:13",
        "name": "linux"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    },
    {
      "ecosystem_specific": {
        "urgency": "not yet assigned"
      },
      "package": {
        "ecosystem": "Debian:14",
        "name": "linux"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "6.19.6-1"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "details": "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.",
  "id": "DEBIAN-CVE-2026-43309",
  "modified": "2026-09-14T16:47:37.822823909Z",
  "published": "2026-05-08T14:16:38.250Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://security-tracker.debian.org/tracker/CVE-2026-43309"
    }
  ],
  "severity": [
    {
      "score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H",
      "type": "CVSS_V3"
    }
  ],
  "upstream": [
    "CVE-2026-43309"
  ]
}