Guest debug suppression via restricted exception injection
Published Jan 11, 2024 · Updated Jun 20, 2025
Protection mechanism failure in AMD EPYC 3rd and 4th Gen processors allows local users with host privileges to suppress guest debug exceptions. A host using restricted injection can withhold hardware debug traps, including single-step and data-breakpoint exceptions, from the guest VM. Host privileges and a SEV-SNP guest with restricted injection enabled are required; guests using alternate injection are not affected.
Summary
What happened
Protection mechanism failure in AMD EPYC 3rd and 4th Gen processors allows local users with host privileges to suppress guest debug exceptions. A host using restricted injection can withhold hardware debug traps, including single-step and data-breakpoint exceptions, from the guest VM. Host privileges and a SEV-SNP guest with restricted injection enabled are required; guests using alternate injection are not affected.
The record
- CVE
- CVE-2023-20573
- Published
- Jan 11, 2024
- Updated
- Jun 20, 2025
- Vendor
- Advanced Micro Devices, Inc.
- Product
- AMD EPYC 4th Gen Processors
- Classifications
- CWE-693
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Jan 11, 2024CVE publishedPublication date reported by the CVE source.
- Jun 20, 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=Various
What conditions does exploitation require?
What is affected?
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