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
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.2%CVSS: 8.8Exploit: None knownExposed services: Not assessed

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.8HIGHmedium confidence
EG Risk
44
EG Risk 44/100

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%
EPSS PROB
0.2%
EPSS %ILE
6th
KEV
Not listed

Published

June 24, 2026

Last Modified

August 5, 2026

Advisory Details (2)

Auto-updated Jun 28, 2026
Patch available.
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(9)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulinux-tools-oracle-7.0 (7.0.0-1008.8) @ resolute2026-09-23ubuntu
ubuntulinux-tools-azure-fde-7.0 (7.0.0-1009.9) @ resolute2026-09-23ubuntu
ubuntulinux-tools-nvidia-hwe-24.04-edge (7.0.0-1016.16) @ resolute2026-09-23ubuntu
ubuntulinux-tools-gcp-edge (7.0.0-1011.11~24.04.1) @ noble2026-09-23ubuntu
ubuntulinux-virtual-hwe-26.04-edge (7.0.0-28.28) @ resolute2026-09-23ubuntu
ubuntulinux-tools-azure-edge (7.0.0-1014.14~24.04.1) @ noble2026-09-23ubuntu
ubuntulinux-tools-raspi-realtime-7.0 (7.0.0-1015.15) @ resolute2026-09-23ubuntu
ubuntulinux-virtual-hwe-24.04-edge (7.0.0-28.28~24.04.1) @ noble2026-09-23ubuntu
ubuntulinux-tools-oem-7.0 (7.0.0-1009.9) @ resolute2026-09-23ubuntu

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 rangeFix by version rangeDependents
linux6.12.100-1 ... 7.0.9-1~bpo13+1 (141 versions)
  • every version up to 7.0.10-1: fixed in 7.0.10-1
—

Weakness Classification(2)

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

All Vendor Advisories

(9)

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 7× in last 7d / 35× 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 291 total refreshes for this CVE.

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

Related CVEs(same vendor + 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 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.2% probability of exploitation in the next 30 days (6th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-52952?
CVE-2026-52952 has a CVSS base score of 8.8 (the CNA's own assessment, by linux; NVD's own analysis pending).
How do I remediate CVE-2026-52952?
A fix for CVE-2026-52952 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-52952 are linked in the Vendor Advisories panel on this page.

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.

Book a Demo →Browse All CVEs