dbcve.org
Race ConditionWeakness · CWE-362

CVE-2025-31944

MEDIUM · 5.3 CVSS v3.1 Published 2026-02-10
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
55/100
Remediation priority · Elevated
Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

A race condition vulnerability exists in Intel TDX Module before version tdx1.5 running in Ring 0 (hypervisor). A privileged local attacker with high-complexity attack capability can exploit this race condition to cause denial of service, impacting system availability.

MitigationUpgrade TDX Module to version tdx1.5 or later. Coordinate with Intel and/or cloud infrastructure provider for firmware/hypervisor updates.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
High
Privileges
High
User interaction
None
Scope
Changed
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:C/C:N/I:N/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify Intel TDX is enabled on the system
    Check the system BIOS/UEFI settings, hypervisor configuration, or system firmware for Intel TDX (Trusted Domain Extensions) enablement status. On Linux systems, you may also check dmesg or /proc/cmdline for TDX-related boot parameters.
    Affected if Intel TDX is present and enabled in the environment
  2. Identify the installed TDX Module version
    Query the hypervisor or firmware for the TDX Module version. This may be accessible through hypervisor-specific tools, BIOS firmware logs, or by reading TDX module information from the hypervisor management interface. Look for version strings like 'tdx1.x' in system logs or hypervisor metadata.
    Affected if The TDX Module version cannot be determined or returns a version string indicating 'tdx1.5' or earlier
  3. Compare the TDX version against tdx1.5
    Parse the identified TDX Module version number and compare it to tdx1.5 using standard version comparison. Versions below tdx1.5 (such as tdx1.0, tdx1.4, etc.) are considered vulnerable.
    Affected if The installed TDX Module version is below tdx1.5 (e.g., tdx1.0, tdx1.4, or any pre-tdx1.5 release)
  4. Confirm local privileged attacker context
    Assess whether the system allows local users with high privileges (Ring 0 or hypervisor-level access) to execute code. This vulnerability requires a privileged local attacker with high-complexity attack capability.
    Affected if Local privileged code execution is possible and the TDX Module version is below tdx1.5

The environment is affected if Intel TDX Module is enabled and the installed version is any release before tdx1.5.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade TDX Module to version tdx1.5 or later. Coordinate with Intel and/or cloud infrastructure provider for firmware/hypervisor updates.

Recommended fix Moderate confidence

TDX Module version tdx1.5

  1. Identify the current version of the Intel TDX Module running on the hypervisor by consulting hypervisor documentation or system logs
  2. Obtain the updated TDX Module version 1.5 from Intel's official channels or your hypervisor vendor
  3. Consult hypervisor vendor documentation for specific procedures to update the TDX Module, as this typically requires hypervisor firmware/microcode update
  4. Apply the TDX Module 1.5 update following vendor-specific upgrade procedures, which usually involves firmware update during system maintenance window
  5. Verify the updated TDX Module version is tdx1.5 or later after applying the update
Caveat Updating TDX Module may require hypervisor firmware update and could require system reboot; verify compatibility with your hypervisor version before applying

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA6.0 h
42.0 hours of engineering $7,360
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $11,776.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-31944 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-31944 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data