Skip to main content
CVE-2025-31944VulnerabilityPublished

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

Affects TDX ModuleSource CVE Database V5

0

Not known to be exploited · CVSS 5.6 Medium.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 4.0 base score
5.6Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.08% chance of exploitation in 30 days – higher than 0% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:L/AC:H/AT:P/PR:H/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:L

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 10 Feb 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

What to do

Affected software

ProductAffectedFixed in
TDX ModuleAffected
  • =before version tdx1.5
Fixed in–

AI-suggested

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.

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.

References

Community reviews

Loading reviews…