Guest compromise via injected int80 syscalls
Published Feb 12, 2024 · Updated May 7, 2025
Protection mechanism failure in Linux kernel before 6.6.7 allows local users with VMM access to manipulate a confidential guest. The TDX and SEV handlers accept a VMM-injected external interrupt on vector 0x80 as a userspace 32-bit syscall, so the current guest registers select the syscall and arguments. Control of the VMM is required; injected calls can alter guest execution, expose data, execute code, or crash the guest.
Summary
What happened
Protection mechanism failure in Linux kernel before 6.6.7 allows local users with VMM access to manipulate a confidential guest. The TDX and SEV handlers accept a VMM-injected external interrupt on vector 0x80 as a userspace 32-bit syscall, so the current guest registers select the syscall and arguments. Control of the VMM is required; injected calls can alter guest execution, expose data, execute code, or crash the guest.
The record
- CVE
- CVE-2024-25744
- Published
- Feb 12, 2024
- Updated
- May 7, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-693, T1499
- Attack vector
- local
- Privileges
- Unavailable
Timeline
How it unfolded
- Feb 12, 2024CVE publishedPublication date reported by the CVE source.
- May 7, 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.
Public exploit references
- Heckler proof-of-concept toolingfunctional · 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