# CVE-2025-31944: Race condition in TDX Module

> A race condition in the Intel TDX Module allows a privileged local attacker to cause a denial of service.

- **Severity:** Medium 5.6 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Feb 2026
- **Updated:** 10 Feb 2026
- **Also known as:** GHSA-9gjv-4x58-j6r8

## What is CVE-2025-31944?

CVE-2025-31944 is a medium-severity vulnerability in TDX Module, published on 10 Feb 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official 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.

Weakness: CWE-362 (Concurrent Execution using Shared Resource with Improper Synchronization)

## Which versions are affected by CVE-2025-31944?


## How do I fix CVE-2025-31944?

No fix has been published for CVE-2025-31944 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-31944 being exploited?

There is no known exploitation of CVE-2025-31944 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-31944 and fix it if it is affected.

What it is: CVE-2025-31944 is a medium-severity vulnerability in TDX Module, published on 10 Feb 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-31944 in the wild and no public exploit code.

Affected product: TDX Module. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-31944/ (Markdown: https://insights.sbomify.com/CVE-2025-31944/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-31944
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-31944
- OSV: https://osv.dev/vulnerability/CVE-2025-31944

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-31944/
Summaries are generated and may contain mistakes; the official description above is the record.