{
  "affected": [
    {
      "ecosystem_specific": {
        "urgency": "not yet assigned"
      },
      "package": {
        "ecosystem": "Debian:14",
        "name": "linux"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "7.0.10-1"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "details": "In the Linux kernel, the following vulnerability has been resolved:  iommu: Fix WARN_ON in __iommu_group_set_domain_nofail() due to reset  In __iommu_group_set_domain_internal(), concurrent domain attachments are rejected when any device in the group is recovering. This is necessary to fence concurrent attachments to a multi-device group where devices might share the same RID due to PCI DMA alias quirks, but triggers the WARN_ON in __iommu_group_set_domain_nofail().  Other IOMMU_SET_DOMAIN_MUST_SUCCEED callers in detach/teardown paths, such as __iommu_group_set_core_domain and __iommu_release_dma_ownership, should not be rejected, as the domain would be freed anyway in these nofail paths while group-\u003edomain is still pointing to it. So pci_dev_reset_iommu_done() could trigger a UAF when re-attaching group-\u003edomain.  Honor the IOMMU_SET_DOMAIN_MUST_SUCCEED flag, allowing the callers through the group-\u003erecovery_cnt fence, so as to update the group-\u003edomain pointer. Instead add a gdev-\u003eblocked check in the device iteration loop, to prevent any concurrent per-device detachment.",
  "id": "DEBIAN-CVE-2026-52952",
  "modified": "2026-09-14T16:47:48.354880229Z",
  "published": "2026-06-24T17:17:05.333Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://security-tracker.debian.org/tracker/CVE-2026-52952"
    }
  ],
  "severity": [
    {
      "score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H",
      "type": "CVSS_V3"
    }
  ],
  "upstream": [
    "CVE-2026-52952"
  ]
}