Guest data corruption via stale TLB reuse
Published Nov 21, 2025 · Updated Nov 21, 2025
Incomplete cleanup in AMD EPYC processors allows local users with administrative privileges to corrupt SEV-SNP guest data. The CPU microcode fails to invalidate TLB state completely, allowing active SNP vCPUs to reuse translations left by other virtual machines. Exploitation requires local administrative control of the hypervisor and the ability to launch an SEV-SNP guest; the reported consequence is guest-data integrity loss, not disclosure or service interruption.
Summary
What happened
Incomplete cleanup in AMD EPYC processors allows local users with administrative privileges to corrupt SEV-SNP guest data. The CPU microcode fails to invalidate TLB state completely, allowing active SNP vCPUs to reuse translations left by other virtual machines. Exploitation requires local administrative control of the hypervisor and the ability to launch an SEV-SNP guest; the reported consequence is guest-data integrity loss, not disclosure or service interruption.
The record
- CVE
- CVE-2025-29934
- Published
- Nov 21, 2025
- Updated
- Nov 21, 2025
- Vendor
- Advanced Micro Devices, Inc.
- Product
- AMD EPYC Embedded 8004 Series Processors
- Classifications
- CWE-459
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Nov 21, 2025CVE publishedPublication date reported by the CVE source.
- Nov 21, 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?
Affected versions are unavailable in this record. Check the vendor advisory for version and patch details.
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
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