CVE-2026-52952

HIGHPre-NVD 8.88.8—
EchelonGraph scoreHIGH confidence

Score 8.8 from GitHub Security Advisory (severity: HIGH) published 2026-06-24. a secondary CVSS source baseline 8.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
8.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 8.8Exploit: 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:

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->domain is still pointing to it. So pci_dev_reset_iommu_done() could trigger a UAF when re-attaching group->domain.

Honor the IOMMU_SET_DOMAIN_MUST_SUCCEED flag, allowing the callers through the group->recovery_cnt fence, so as to update the group->domain pointer. Instead add a gdev->blocked check in the device iteration loop, to prevent any concurrent per-device detachment.

CVSS v3
8.8
EG Score
8.8(high)
EPSS
3.1%
KEV
Not listed

Published

June 24, 2026

Last Modified

June 30, 2026

Advisory Details (2)

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

iommu: Fix WARN_ON in __iommu_group_set_domain_nofail() due to reset - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/8fc289e809f3eb7e36cadc4684ab6fad747a5a93
generic

iommu: Fix WARN_ON in __iommu_group_set_domain_nofail() due to reset - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/5474e6e17a262db45c60575c73f70210f5c7001f

Vendor Advisories for CVE-2026-52952(1)

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

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 34× in last 7d / 46× 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.

  1. 2026-07-07 06:15 UTCEG score recompute
  2. 2026-07-07 06:15 UTCGHSA enrichment
  3. 2026-07-06 19:10 UTCEG score recompute
  4. 2026-07-06 19:10 UTCGHSA enrichment
  5. 2026-07-06 16:27 UTCEPSS rescore
  6. 2026-07-06 16:27 UTCEPSS rescore
  7. 2026-07-06 08:03 UTCEG score recompute
  8. 2026-07-06 08:03 UTCGHSA enrichment
  9. 2026-07-06 02:23 UTCEPSS rescore
  10. 2026-07-06 02:23 UTCEPSS rescore
  11. 2026-07-05 20:43 UTCEG score recompute
  12. 2026-07-05 20:43 UTCGHSA enrichment
  13. 2026-07-05 09:38 UTCEG score recompute
  14. 2026-07-05 09:38 UTCGHSA enrichment
  15. 2026-07-04 22:34 UTCEG score recompute
  16. 2026-07-04 22:33 UTCGHSA enrichment
  17. 2026-07-04 11:28 UTCEG score recompute
  18. 2026-07-04 11:28 UTCGHSA enrichment
  19. 2026-07-04 06:31 UTCEPSS rescore
  20. 2026-07-04 00:24 UTCEG score recompute
  21. 2026-07-04 00:24 UTCGHSA enrichment
  22. 2026-07-03 13:21 UTCEG score recompute
  23. 2026-07-03 13:20 UTCGHSA enrichment
  24. 2026-07-03 02:16 UTCEG score recompute
  25. 2026-07-03 02:16 UTCGHSA enrichment
Show 21 more
  1. 2026-07-02 15:11 UTCEG score recompute
  2. 2026-07-02 15:11 UTCGHSA enrichment
  3. 2026-07-02 04:03 UTCEG score recompute
  4. 2026-07-02 04:03 UTCGHSA enrichment
  5. 2026-07-01 16:59 UTCEG score recompute
  6. 2026-07-01 16:59 UTCGHSA enrichment
  7. 2026-07-01 05:55 UTCEG score recompute▲ 8.80
  8. 2026-07-01 05:55 UTCGHSA enrichment
  9. 2026-06-30 23:22 UTCEPSS rescore
  10. 2026-06-29 14:06 UTCEPSS rescore
  11. 2026-06-29 14:06 UTCEPSS rescore
  12. 2026-06-28 14:07 UTCEPSS rescore
  13. 2026-06-28 07:52 UTCMITRE cvelistV5CVSS v3 → 8.8 · severity → HIGH
  14. 2026-06-28 04:56 UTCEPSS rescore
  15. 2026-06-28 04:56 UTCEPSS rescore
  16. 2026-06-28 00:12 UTCEG score recompute
  17. 2026-06-28 00:12 UTCGHSA enrichment
  18. 2026-06-27 03:08 UTCEPSS rescore
  19. 2026-06-25 13:49 UTCEPSS rescore
  20. 2026-06-24 18:30 UTCEG score recompute
  21. 2026-06-24 18:02 UTCNVD updatefirst tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-52952?
CVE-2026-52952 is a high vulnerability published on June 24, 2026. In the Linux kernel, the following vulnerability has been resolved: iommu: Fix WARNON in iommugroupsetdomain_nofail() due to reset In iommugroupsetdomaininternal(), concurrent domain attachments are rejected when any device in the group is recovering. This is necessary to fence concurrent…
When was CVE-2026-52952 disclosed?
CVE-2026-52952 was first published in the National Vulnerability Database on June 24, 2026, with the most recent update on June 30, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-52952 actively exploited?
CVE-2026-52952 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 3.1% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-52952?
CVE-2026-52952 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2026-52952?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-52952, 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-52952

Explore →

Is Your Infrastructure Affected by CVE-2026-52952?

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

Start Free Scan →Browse All CVEs