CVE-2026-53053

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 — Patch released 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/amd: Fix clone_alias() to use the original device's devid

Currently clone_alias() assumes first argument (pdev) is always the original device pointer. This function is called by pci_for_each_dma_alias() which based on topology decides to send original or alias device details in first argument.

This meant that the source devid used to look up and copy the DTE may be incorrect, leading to wrong or stale DTE entries being propagated to alias device.

Fix this by passing the original pdev as the opaque data argument to both the direct clone_alias() call and pci_for_each_dma_alias(). Inside clone_alias(), retrieve the original device from data and compute devid from it.

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
3%
KEV
Not listed

Published

June 24, 2026

Last Modified

August 5, 2026

Advisory Details (4)

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

iommu/amd: Fix clone_alias() to use the original device's devid - kernel/git/stable/linux.git - Linux kernel stable tree

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

iommu/amd: Fix clone_alias() to use the original device's devid - kernel/git/stable/linux.git - Linux kernel stable tree

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

iommu/amd: Fix clone_alias() to use the original device's devid - kernel/git/stable/linux.git - Linux kernel stable tree

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

iommu/amd: Fix clone_alias() to use the original device's devid - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/20b3c566e2702e5d4d0545be8a97029a2eebcc0e

Vendor Advisories for CVE-2026-53053(4)

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

Patch Availability(11)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-tools-raspi-realtime-7.0 (7.0.0-1015.15) @ resolute2026-09-18ubuntu
ubuntulinux-virtual-hwe-24.04-edge (7.0.0-28.28~24.04.1) @ noble2026-09-18ubuntu
ubuntulinux-tools-oracle-7.0 (7.0.0-1008.8) @ resolute2026-09-18ubuntu
ubuntulinux-tools-nvidia-hwe-24.04-edge (7.0.0-1016.16) @ resolute2026-09-18ubuntu
ubuntulinux-tools-gcp-edge (7.0.0-1011.11~24.04.1) @ noble2026-09-18ubuntu
ubuntulinux-tools-nvidia-hwe-26.04 (7.0.0-2016.16) @ resolute2026-09-18ubuntu
ubuntulinux-virtual-hwe-26.04-edge (7.0.0-28.28) @ resolute2026-09-18ubuntu
ubuntulinux-tools-oem-7.0 (7.0.0-1009.9) @ resolute2026-09-18ubuntu
ubuntulinux-tools-azure-fde-7.0 (7.0.0-1009.9) @ resolute2026-09-18ubuntu
redhatkernel-0:5.14.0-687.47.1.el9_82026-09-14redhat
redhatkernel-0:6.12.0-211.50.1.el10_22026-09-01redhat

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

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
linux5.10.103-1 ... 7.2~rc5-1~exp1 (496 versions)——
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 7.2~rc7-1~exp1 (350 versions)——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.94-1~bpo12+1 (27 versions)6.12.94-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.0.9-1~bpo13+1 (140 versions)7.0.10-1—

Additional Vendor Advisories

(9)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 15× in last 7d / 59× 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 260 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-53053?
CVE-2026-53053 is a high vulnerability published on June 24, 2026. In the Linux kernel, the following vulnerability has been resolved: iommu/amd: Fix clone_alias() to use the original device's devid Currently clone_alias() assumes first argument (pdev) is always the original device pointer. This function is called by pciforeachdmaalias() which based on topology…
When was CVE-2026-53053 disclosed?
CVE-2026-53053 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-53053 actively exploited?
CVE-2026-53053 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 97.1% of all scored CVEs.
What is the CVSS score of CVE-2026-53053?
CVE-2026-53053 has a CVSS v4.0 base score of 8.8 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-53053?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-53053, 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-53053

Explore →

Is Your Infrastructure Affected by CVE-2026-53053?

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

Start Free Scan →Browse All CVEs