Guest memory compromise via unchecked #VC exit reason
Published May 17, 2024 · Updated Mar 27, 2025
Improper #VC handling in the Linux kernel before 6.9 allows attackers controlling a hypervisor to read or write SEV-ES and SEV-SNP guest memory. The SEV exception handler trusted an injected exit reason without verifying that the instruction bytes at the guest's saved instruction pointer matched it. Control of the hypervisor is required, and successful injection breaks guest confidentiality and integrity, including arbitrary code execution.
Summary
What happened
Improper #VC handling in the Linux kernel before 6.9 allows attackers controlling a hypervisor to read or write SEV-ES and SEV-SNP guest memory. The SEV exception handler trusted an injected exit reason without verifying that the instruction bytes at the guest's saved instruction pointer matched it. Control of the hypervisor is required, and successful injection breaks guest confidentiality and integrity, including arbitrary code execution.
The record
- CVE
- CVE-2024-25742
- Published
- May 17, 2024
- Updated
- Mar 27, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-828, T1068
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- May 17, 2024CVE publishedPublication date reported by the CVE source.
- Mar 27, 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
- WeSee proof-of-conceptfunctional · demonstrated
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