Device isolation bypass via incorrect DTE cloning
Published Jun 24, 2026 · Updated Jun 24, 2026
AMD IOMMU isolation failure in affected Linux Kernel releases allows local users to corrupt device translation state through PCI DMA aliases. clone_alias() treats its callback pdev argument as the original device and derives the source devid from it, so topology-dependent alias callbacks copy a wrong or stale DTE. Reachability requires an AMD IOMMU, a PCI device with DMA aliases, and local control of an assigned device; the resulting DTE can expose or alter memory across the intended isolation boundary or interrupt service.
Summary
What happened
AMD IOMMU isolation failure in affected Linux Kernel releases allows local users to corrupt device translation state through PCI DMA aliases. clone_alias() treats its callback pdev argument as the original device and derives the source devid from it, so topology-dependent alias callbacks copy a wrong or stale DTE. Reachability requires an AMD IOMMU, a PCI device with DMA aliases, and local control of an assigned device; the resulting DTE can expose or alter memory across the intended isolation boundary or interrupt service.
The record
- CVE
- CVE-2026-53053
- Published
- Jun 24, 2026
- Updated
- Jun 24, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- Unavailable
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 24, 2026CVE publishedPublication date reported by the CVE source.
- Jun 24, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=1f03a258f20f1699ede29bb40804074db9398a0d
- Affected versionversion=3332364e4ebc0581d133a334645a20fd13b580f1 <20b3c566e2702e5d4d0545be8a97029a2eebcc0e
- Affected versionversion=3332364e4ebc0581d133a334645a20fd13b580f1 <dae251ff11d2d2208a029f98923756831cefec46
- Affected versionversion=3332364e4ebc0581d133a334645a20fd13b580f1 <dbd76a537d8cb814e7f5b795ab21ecb7949c821d
- Affected versionversion=3332364e4ebc0581d133a334645a20fd13b580f1 <faad224fe0f0857a04ff2eb3c90f0de57f47d0f3
- Affected versionversion=5.4.17 <5.5
- Affected versionversion=5.5
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
No sourced classifications are available.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo