CVE-2025-31944
Race Condition in Intel TDX Module Causes Denial of Service
Publication date: 2026-02-10
Last updated on: 2026-02-10
Assigner: Intel Corporation
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| intel | tdx_module | to tdx1.5 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-362 | The product contains a concurrent code sequence that requires temporary, exclusive access to a shared resource, but a timing window exists in which the shared resource can be modified by another code sequence operating concurrently. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability is a race condition found in some versions of the Intel TDX Module before version tdx1.5, specifically within Ring 0 of the hypervisor. A race condition occurs when multiple processes access shared resources concurrently, leading to unexpected behavior. In this case, an authorized adversary with privileged user access can exploit this race condition through a complex attack to cause a denial of service (DoS) on the system.
The attack requires local access and does not need special internal knowledge or user interaction, but it is complex and requires high privileges.
How can this vulnerability impact me? :
This vulnerability primarily impacts the availability of the affected system, potentially causing a denial of service. It does not affect the confidentiality or integrity of the system.
- An authorized user with high privileges could exploit this to disrupt system operations.
- The attack requires local access and is complex, so it is less likely to be exploited remotely or by unprivileged users.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know
How can this vulnerability be detected on my network or system? Can you suggest some commands?
I don't know
What immediate steps should I take to mitigate this vulnerability?
I don't know