CVE-2026-53053

HIGHPre-NVD 8.88.8—
EchelonGraph scoreHIGH confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
8.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 8.8Exploit: 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/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(high)
EPSS
2.9%
KEV
Not listed

Published

June 24, 2026

Last Modified

June 28, 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(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 30× in last 7d / 42× 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 19:50 UTCEG score recompute
  2. 2026-07-06 19:50 UTCGHSA enrichment
  3. 2026-07-06 16:27 UTCEPSS rescore
  4. 2026-07-06 16:27 UTCEPSS rescore
  5. 2026-07-06 06:40 UTCEG score recompute
  6. 2026-07-06 06:40 UTCGHSA enrichment
  7. 2026-07-06 02:23 UTCEPSS rescore
  8. 2026-07-06 02:23 UTCEPSS rescore
  9. 2026-07-05 17:31 UTCEG score recompute
  10. 2026-07-05 17:31 UTCGHSA enrichment
  11. 2026-07-05 04:22 UTCEG score recompute
  12. 2026-07-05 04:22 UTCGHSA enrichment
  13. 2026-07-05 02:31 UTCEPSS rescore
  14. 2026-07-05 02:30 UTCEPSS rescore
  15. 2026-07-04 15:10 UTCEG score recompute
  16. 2026-07-04 15:10 UTCGHSA enrichment
  17. 2026-07-04 02:01 UTCEG score recompute
  18. 2026-07-04 02:00 UTCGHSA enrichment
  19. 2026-07-03 12:50 UTCEG score recompute
  20. 2026-07-03 12:49 UTCGHSA enrichment
  21. 2026-07-02 22:51 UTCEG score recompute
  22. 2026-07-02 22:51 UTCGHSA enrichment
  23. 2026-07-02 09:43 UTCEG score recompute
  24. 2026-07-02 09:42 UTCGHSA enrichment
  25. 2026-07-01 20:33 UTCEG score recompute
Show 17 more
  1. 2026-07-01 20:33 UTCGHSA enrichment
  2. 2026-07-01 15:07 UTCEPSS rescore
  3. 2026-07-01 07:24 UTCEG score recompute▲ 8.80
  4. 2026-07-01 07:24 UTCGHSA enrichment
  5. 2026-06-30 23:22 UTCEPSS rescore
  6. 2026-06-29 14:06 UTCEPSS rescore
  7. 2026-06-29 14:06 UTCEPSS rescore
  8. 2026-06-28 14:07 UTCEPSS rescore
  9. 2026-06-28 07:52 UTCMITRE cvelistV5CVSS v3 → 8.8 · severity → HIGH
  10. 2026-06-28 04:56 UTCEPSS rescore
  11. 2026-06-28 04:56 UTCEPSS rescore
  12. 2026-06-28 00:50 UTCEG score recompute
  13. 2026-06-28 00:50 UTCGHSA enrichment
  14. 2026-06-27 03:08 UTCEPSS rescore
  15. 2026-06-25 13:49 UTCEPSS rescore
  16. 2026-06-24 18:17 UTCEG score recompute
  17. 2026-06-24 18:03 UTCNVD updatefirst tracked

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 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-53053 actively exploited?
CVE-2026-53053 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 2.9% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-53053?
CVE-2026-53053 has a CVSS v3 base score of 8.8 (NVD).
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

Explore the affected products and dependency analysis for 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