CVE-2025-20044 Race condition in Intel(R) TDX Module firmware
Medium 5.6
Published
Updated
Check this codebase for CVE-2025-20044 and fix it if it is affected.
What it is: CVE-2025-20044 is a medium-severity vulnerability in Intel(R) TDX Module firmware, published on 12 Aug 2025. 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-20044 in the wild and no public exploit code.
Affected product: Intel(R) TDX Module firmware. 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-20044/ (Markdown: https://insights.sbomify.com/CVE-2025-20044/index.md)
A local privileged user can escalate privileges due to improper locking in Intel TDX Module firmware.
- Exploited in the wild
- Not known
- Login needed
- An administrator
- Attackable
- Local or same network only
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2025-20044?
CVE-2025-20044 is a medium-severity vulnerability in Intel(R) TDX Module firmware, published on 12 Aug 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Official description
Improper locking for some Intel(R) TDX Module firmware before version 1.5.13 may allow a privileged user to potentially enable escalation of privilege via local access.
Weakness: CWE-667
Which versions are affected by CVE-2025-20044?
How do I fix CVE-2025-20044?
No fix has been published for CVE-2025-20044 yet. Limit exposure of the affected software until one is available.
Is CVE-2025-20044 being exploited?
There is no known exploitation of CVE-2025-20044 in the wild and no public exploit code.
Sources
Also known as GHSA-w3qv-8x8p-58q9.