Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2025-31944: Denial of Service in TDX Module

0
Medium
VulnerabilityCVE-2025-31944cvecve-2025-31944
Published: Tue Feb 10 2026 (02/10/2026, 16:25:39 UTC)
Source: CVE Database V5
Product: TDX Module

Description

Race condition for some TDX Module before version tdx1.5 within Ring 0: Hypervisor may allow a denial of service. Authorized adversary with a privileged user combined with a high complexity attack may enable denial of service. This result may potentially occur via local access when attack requirements are present without special internal knowledge and requires no user interaction. The potential vulnerability may impact the confidentiality (none), integrity (none) and availability (high) of the vulnerable system, resulting in subsequent system confidentiality (none), integrity (none) and availability (low) impacts.

AI-Powered Analysis

AILast updated: 02/10/2026, 16:50:45 UTC

Technical Analysis

CVE-2025-31944 identifies a race condition vulnerability in Intel's Trusted Domain Extensions (TDX) Module prior to version tdx1.5. The TDX Module operates within Ring 0 of the hypervisor, providing hardware-based isolation for virtual machines. The race condition flaw allows an authorized adversary with privileged user access to induce a denial of service (DoS) condition by exploiting timing issues in the module's handling of certain operations. The attack requires local access and elevated privileges, with a high complexity level, meaning it is not trivial to execute. No user interaction or special internal knowledge is necessary, but the attacker must already have privileged access on the host system. The vulnerability impacts availability by potentially causing system or hypervisor instability, leading to service disruption. Confidentiality and integrity are not affected, as the flaw does not allow data leakage or unauthorized modification. The CVSS 4.0 score of 5.6 (medium) reflects these characteristics, with attack vector local, attack complexity high, privileges required high, and no user interaction needed. No public exploits have been reported, and no patches are linked in the provided data, indicating organizations should monitor Intel advisories for updates. The vulnerability is relevant to environments deploying Intel TDX-enabled platforms, particularly those relying on hardware virtualization and isolation for security.

Potential Impact

For European organizations, the primary impact of CVE-2025-31944 is on system availability. Enterprises and cloud service providers using Intel TDX-enabled hardware may experience service interruptions or system crashes if the vulnerability is exploited. This can affect critical infrastructure, virtualized environments, and cloud workloads that depend on TDX for secure isolation. Although confidentiality and integrity are not compromised, operational disruption can lead to downtime, impacting business continuity and service level agreements. Organizations with high reliance on virtualization security features may face increased risk of denial of service attacks from insiders or compromised privileged accounts. The requirement for privileged local access limits the threat to internal actors or attackers who have already breached perimeter defenses. Nevertheless, the potential for high-impact availability disruption necessitates proactive mitigation, especially in sectors like finance, telecommunications, and government services where uptime is critical.

Mitigation Recommendations

To mitigate CVE-2025-31944, European organizations should: 1) Monitor Intel's official security advisories and apply patches or firmware updates for the TDX Module as soon as they become available, especially upgrading to version tdx1.5 or later. 2) Enforce strict access controls and privilege management to limit the number of users with elevated privileges on systems running TDX-enabled hypervisors. 3) Implement robust monitoring and anomaly detection to identify unusual activity indicative of race condition exploitation attempts. 4) Use virtualization security best practices, including isolating management interfaces and restricting local access to hypervisor hosts. 5) Conduct regular security audits and penetration testing focusing on privilege escalation and local attack vectors. 6) Consider compensating controls such as host-based intrusion prevention systems (HIPS) to detect and block suspicious race condition exploitation behaviors. 7) Maintain incident response readiness to quickly address potential denial of service incidents affecting critical virtualized infrastructure.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

Data Version
5.2
Assigner Short Name
intel
Date Reserved
2025-04-15T21:16:05.092Z
Cvss Version
4.0
State
PUBLISHED

Threat ID: 698b5d5d4b57a58fa119cf53

Added to database: 2/10/2026, 4:31:25 PM

Last enriched: 2/10/2026, 4:50:45 PM

Last updated: 2/20/2026, 10:54:08 PM

Views: 28

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats