Privileged service interruption via hypervisor race condition
Published Feb 10, 2026 · Updated Feb 10, 2026
Race condition in Intel TDX Module before 1.5 allows local privileged hypervisor users to interrupt service through concurrent execution. Intel identifies the locus only as the Ring 0 hypervisor and has not disclosed the shared resource, synchronization error, or triggering operation. Exploitation requires high complexity and attack requirements; it disrupts module availability and has a bounded low downstream availability impact.
Summary
What happened
Race condition in Intel TDX Module before 1.5 allows local privileged hypervisor users to interrupt service through concurrent execution. Intel identifies the locus only as the Ring 0 hypervisor and has not disclosed the shared resource, synchronization error, or triggering operation. Exploitation requires high complexity and attack requirements; it disrupts module availability and has a bounded low downstream availability impact.
The record
- CVE
- CVE-2025-31944
- Published
- Feb 10, 2026
- Updated
- Feb 10, 2026
- Vendor
- Topcon Positioning Systems, Inc.
- Product
- Intel TDX Module
- Classifications
- CWE-362, T1499
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Feb 10, 2026CVE publishedPublication date reported by the CVE source.
- Feb 10, 2026Record 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=before version tdx1.5
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