CVE-2026-53053: iommu/amd: Fix clone_alias() to use the original device's devid

criticalCVSS 9.8CVE-2026-53053

CSIRTS triage

Other

What: A critical issue exists in 'clone_alias()' that needs to use the original device's devid.
Who is affected: Deployments using the affected IOMMU subsystem.
Urgency: Remediation is critical due to the high severity and potential for exploitation.
Action: Apply the relevant patches to fix this issue.

AI-assisted analysis generated from the source advisory — verify against the original.

Details

Source: Microsoft Security Response Center (INTL · vendor-psirt · site)
Severity: critical — CVSS 9.8
Published: 2026-06-09
Exploitation: Not in CISA KEV at last sync

Original advisory: https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-53053

Exploitation outlook

EPSS (FIRST.org) estimates each CVE’s probability of exploitation in the next 30 days — here is the CSIRTS.com read on those numbers.

Low exploitation riskCVE-2026-530530.13% 30-day exploitation probability — currently an unlikely target, but scores change as exploit code circulates. Riskier than 3% of all scored CVEs.

Referenced CVEs

CVE	CSIRTS overview	External
CVE-2026-53053	coverage & exploitation status	NVD · CVE.org

Recent advisories for iommu/amd

A cluster of recent advisories against the same product widens the attack surface — attackers routinely chain freshly published CVEs on one product, so review these together.

unknownCVE-2026-53283: In the Linux kernel, the following vulnerability has been resolved: iommu/amd: Bounds-check de…nvd · 2026-06-26