Cross-guest data disclosure via uninitialized firmware memory
Published Feb 13, 2024 · Updated Mar 20, 2025
Improper memory initialization in AMD SEV firmware on 3rd and 4th Gen EPYC processors allows local users to read stale guest data. The SEV firmware fails to initialize memory before reuse, leaving data from one confidential guest accessible from another guest context. Exploitation requires high local privileges on an affected SEV-SNP host and exposes residual guest data without reported integrity or availability effects.
Summary
What happened
Improper memory initialization in AMD SEV firmware on 3rd and 4th Gen EPYC processors allows local users to read stale guest data. The SEV firmware fails to initialize memory before reuse, leaving data from one confidential guest accessible from another guest context. Exploitation requires high local privileges on an affected SEV-SNP host and exposes residual guest data without reported integrity or availability effects.
The record
- CVE
- CVE-2023-31346
- Published
- Feb 13, 2024
- Updated
- Mar 20, 2025
- Vendor
- Advanced Micro Devices, Inc.
- Product
- AMD EPYC 4th Gen Processors
- Classifications
- CWE-284, T1005
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Feb 13, 2024CVE publishedPublication date reported by the CVE source.
- Mar 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.
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