CVE-2026-52952

HIGHPre-NVD 8.88.8—
EchelonGraph scoreMEDIUM confidence

Score 8.8 from GitHub Security Advisory (severity: HIGH) published 2026-06-24. the CNA's CVSS baseline 8.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cna:linux, epss, ghsa
Trending — 4 sources updated this week
8.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.8Exploit: None knownExposed: 0

A fix is available — apply it.

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(medium)
EG Risk
44(Track)
EG Risk 44/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity88% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
7%
KEV
Not listed

Published

June 24, 2026

Last Modified

August 5, 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.

Patch Availability(7)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-tools-nvidia-hwe-24.04-edge (7.0.0-1016.16) @ resolute2026-08-25ubuntu
ubuntulinux-virtual-hwe-26.04-edge (7.0.0-28.28) @ resolute2026-08-25ubuntu
ubuntulinux-virtual-hwe-24.04-edge (7.0.0-28.28~24.04.1) @ noble2026-08-25ubuntu
ubuntulinux-tools-oem-7.0 (7.0.0-1009.9) @ resolute2026-08-25ubuntu
ubuntulinux-tools-oracle-7.0 (7.0.0-1008.8) @ resolute2026-08-25ubuntu
ubuntulinux-tools-raspi-realtime-7.0 (7.0.0-1015.15) @ resolute2026-08-25ubuntu
ubuntulinux-tools-azure-fde-7.0 (7.0.0-1009.9) @ resolute2026-08-25ubuntu

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.0.9-1~bpo13+1 (137 versions)7.0.10-1—

Weakness Classification(2)

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

All Vendor Advisories

(7)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 32× in last 7d / 157× 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 238 total refreshes for this CVE.

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

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 August 5, 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 0% probability of exploitation in the next 30 days, which ranks it in the top 92.7% of all scored CVEs.
What is the CVSS score of CVE-2026-52952?
CVE-2026-52952 has a CVSS v4.0 base score of 8.8 (CNA self-assessment; NVD's own analysis pending).
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

See which npm, PyPI, Go, and Maven packages are affected by 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