CVE-2026-52953

HIGHPre-NVD 7.17.1—
EchelonGraph scoreHIGH confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
7.1
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.1Exploit: 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/vt-d: Fix oops due to out of scope access

Below oops triggers when kill QEMU process:

Oops: general protection fault, probably for non-canonical address 0x7fffffff844eaaa7: 0000 [#1] SMP NOPTI Call Trace: do_raw_spin_lock+0xaa/0xc0 _raw_spin_lock_irqsave+0x21/0x40 domain_remove_dev_pasid+0x52/0x160 intel_nested_set_dev_pasid+0x1b9/0x1e0 __iommu_set_group_pasid+0x56/0x120 pci_dev_reset_iommu_done+0xe3/0x180 pcie_flr+0x65/0x160 __pci_reset_function_locked+0x5b/0x120 vfio_pci_core_close_device+0x63/0xe0 [vfio_pci_core] vfio_df_close+0x4f/0xa0 vfio_df_unbind_iommufd+0x2d/0x60 vfio_device_fops_release+0x3e/0x40 __fput+0xe5/0x2c0 task_work_run+0x58/0xa0 do_exit+0x2c8/0x600 do_group_exit+0x2f/0xa0 get_signal+0x863/0x8c0 arch_do_signal_or_restart+0x24/0x100 exit_to_user_mode_loop+0x87/0x380 do_syscall_64+0x2ff/0x11e0 entry_SYSCALL_64_after_hwframe+0x76/0x7e

The global static blocked domain is a dummy domain without corresponding dmar_domain structure, accessing beyond iommu_domain structure triggers oops easily. Fix it by return early in domain_remove_dev_pasid() like identity domain.

CVSS v3
7.1
EG Score
7.1(high)
EPSS
3.2%
KEV
Not listed

Published

June 24, 2026

Last Modified

June 28, 2026

Advisory Details (3)

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

iommu/vt-d: Fix oops due to out of scope access - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/a6dea58d8625c06b9654c0555f101742481335c3
generic

iommu/vt-d: Fix oops due to out of scope access - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/88397fad7914ee74a7880fa5ce01f9eb6bfe0743
generic

iommu/vt-d: Fix oops due to out of scope access - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/1e659db468476733d217c1314c1e0d9244356d6c

Vendor Advisories for CVE-2026-52953(2)

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

Data Freshness Timeline

(refreshed 32× in last 7d / 44× 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-06 17:42 UTCEG score recompute
  2. 2026-07-06 17:42 UTCGHSA enrichment
  3. 2026-07-06 06:26 UTCEG score recompute
  4. 2026-07-06 06:26 UTCGHSA enrichment
  5. 2026-07-06 02:23 UTCEPSS rescore
  6. 2026-07-06 02:23 UTCEPSS rescore
  7. 2026-07-05 19:15 UTCEG score recompute
  8. 2026-07-05 19:15 UTCGHSA enrichment
  9. 2026-07-05 08:05 UTCEG score recompute
  10. 2026-07-05 08:05 UTCGHSA enrichment
  11. 2026-07-04 20:55 UTCEG score recompute
  12. 2026-07-04 20:55 UTCGHSA enrichment
  13. 2026-07-04 09:46 UTCEG score recompute
  14. 2026-07-04 09:45 UTCGHSA enrichment
  15. 2026-07-04 06:31 UTCEPSS rescore
  16. 2026-07-03 22:36 UTCEG score recompute
  17. 2026-07-03 22:36 UTCGHSA enrichment
  18. 2026-07-03 11:27 UTCEG score recompute
  19. 2026-07-03 11:27 UTCGHSA enrichment
  20. 2026-07-03 00:15 UTCEG score recompute
  21. 2026-07-03 00:15 UTCGHSA enrichment
  22. 2026-07-02 13:06 UTCEG score recompute
  23. 2026-07-02 13:05 UTCGHSA enrichment
  24. 2026-07-02 13:03 UTCGHSA enrichment
  25. 2026-07-02 01:53 UTCEG score recompute
Show 19 more
  1. 2026-07-02 01:53 UTCGHSA enrichment
  2. 2026-07-01 15:07 UTCEPSS rescore
  3. 2026-07-01 14:44 UTCEG score recompute
  4. 2026-07-01 14:44 UTCGHSA enrichment
  5. 2026-07-01 03:35 UTCEG score recompute▲ 7.10
  6. 2026-07-01 03:35 UTCGHSA enrichment
  7. 2026-06-30 23:22 UTCEPSS rescore
  8. 2026-06-29 14:06 UTCEPSS rescore
  9. 2026-06-29 14:06 UTCEPSS rescore
  10. 2026-06-28 14:07 UTCEPSS rescore
  11. 2026-06-28 07:52 UTCMITRE cvelistV5CVSS v3 → 7.1 · severity → HIGH
  12. 2026-06-28 04:56 UTCEPSS rescore
  13. 2026-06-28 04:56 UTCEPSS rescore
  14. 2026-06-27 23:03 UTCEG score recompute
  15. 2026-06-27 23:02 UTCGHSA enrichment
  16. 2026-06-27 03:08 UTCEPSS rescore
  17. 2026-06-25 13:49 UTCEPSS rescore
  18. 2026-06-24 18:30 UTCEG score recompute
  19. 2026-06-24 18:02 UTCNVD updatefirst tracked

Frequently asked(5)

What is CVE-2026-52953?
CVE-2026-52953 is a high vulnerability published on June 24, 2026. In the Linux kernel, the following vulnerability has been resolved: iommu/vt-d: Fix oops due to out of scope access Below oops triggers when kill QEMU process: Oops: general protection fault, probably for non-canonical address 0x7fffffff844eaaa7: 0000 [#1] SMP NOPTI Call Trace: <TASK>…
When was CVE-2026-52953 disclosed?
CVE-2026-52953 was first published in the National Vulnerability Database on June 24, 2026, with the most recent update on June 28, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-52953 actively exploited?
CVE-2026-52953 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 3.2% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-52953?
CVE-2026-52953 has a CVSS v3 base score of 7.1 (NVD).
How do I remediate CVE-2026-52953?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-52953, 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-52953

Explore →

Is Your Infrastructure Affected by CVE-2026-52953?

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

Start Free Scan →Browse All CVEs