Guest-domain integrity loss via stale VT-d assignment
Published Mar 20, 2024 · Updated Nov 4, 2025
Improper device quarantine in Xen 4.17 and later allows guest OS users to retain access after a passed-through PCI device is removed. In the Intel VT-d IOMMU path, a misplaced preprocessor branch makes device-removal logic skip quarantine when CONFIG_HVM is disabled. Exposure requires x86 hardware with an Intel-compatible VT-d IOMMU and PCI passthrough to an untrusted or semi-trusted guest; the removed device retains access to its former domain.
Summary
What happened
Improper device quarantine in Xen 4.17 and later allows guest OS users to retain access after a passed-through PCI device is removed. In the Intel VT-d IOMMU path, a misplaced preprocessor branch makes device-removal logic skip quarantine when CONFIG_HVM is disabled. Exposure requires x86 hardware with an Intel-compatible VT-d IOMMU and PCI passthrough to an untrusted or semi-trusted guest; the removed device retains access to its former domain.
The record
- CVE
- CVE-2023-46840
- Published
- Mar 20, 2024
- Updated
- Nov 4, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-670, T1068
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Mar 20, 2024CVE publishedPublication date reported by the CVE source.
- Nov 4, 2025Record 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.
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
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