CVE-2026-52953

HIGHPre-NVD 7.17.1—
EchelonGraph scoreMEDIUM confidence

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

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

A fix is available — apply it.

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(medium)
EG Risk
37(Track)
EG Risk 37/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
Severity71% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
3%
KEV
Not listed

Published

June 24, 2026

Last Modified

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

Patch Availability(8)

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

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

(2 across 2 ecosystems)
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.2~rc7-1~exp1 (174 versions)——
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.0.9-1~bpo13+1 (140 versions)7.0.10-1—

Weakness Classification(1)

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

All Vendor Advisories

(8)

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 5× in last 7d / 86× 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 263 total refreshes for this CVE.

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

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 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-52953 actively exploited?
CVE-2026-52953 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 96.8% of all scored CVEs.
What is the CVSS score of CVE-2026-52953?
CVE-2026-52953 has a CVSS v4.0 base score of 7.1 (CNA self-assessment; NVD's own analysis pending).
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

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