Host service interruption via broken IOMMU mappings
Published Apr 5, 2022 · Updated Aug 3, 2024
Improper IOMMU mapping handling in Xen allows guest OS users to trigger IOMMU faults or memory corruption through passed-through PCI devices. Xen fails to keep Intel VT-d RMRR or AMD-Vi unity-map regions continuously accessible after activating an associated device, allowing later DMA or interrupts to reach an invalid mapping state. Exploitation requires an x86 guest with a physical device assigned and an active IOMMU; the result is system-specific, with host-wide service interruption identified as the expected outcome.
Summary
What happened
Improper IOMMU mapping handling in Xen allows guest OS users to trigger IOMMU faults or memory corruption through passed-through PCI devices. Xen fails to keep Intel VT-d RMRR or AMD-Vi unity-map regions continuously accessible after activating an associated device, allowing later DMA or interrupts to reach an invalid mapping state. Exploitation requires an x86 guest with a physical device assigned and an active IOMMU; the result is system-specific, with host-wide service interruption identified as the expected outcome.
The record
- CVE
- CVE-2022-26358
- Published
- Apr 5, 2022
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Apr 5, 2022CVE publishedPublication date reported by the CVE source.
- Aug 3, 2024Record 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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
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