dbcve.org
Race ConditionWeakness · CWE-362

CVE-2025-30513

HIGH · 7.9 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 →
81/100
Remediation priority · High
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 within Ring 0: Hypervisor may allow an escalation of privilege. System software adversary with a privileged user combined with a low complexity attack may enable escalation of privilege. This result may potentially occur via local access when attack requirements are not present with special internal knowledge and requires no user interaction. The potential vulnerability may impact the confidentiality (high), integrity (high) and availability (none) of the vulnerable system, resulting in subsequent system confidentiality (none), integrity (none) and availability (none) 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's Trust Domain Extensions (TDX) Module hypervisor component running at Ring 0. An attacker with privileged user access, local system access, and special internal knowledge can exploit a timing-based race condition to escalate privileges, potentially achieving higher privileges within the TDX environment. The vulnerability impacts confidentiality and integrity but not availability.

MitigationApply Intel microcode/firmware updates and any TDX Module patches when available; restrict local access to trusted privileged users; review and harden TDX deployment configurations to minimize attack surface.

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
Low
Privileges
High
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
None

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

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 TDX is enabled on the system
    Check if Intel Trust Domain Extensions is active by inspecting CPU capability flags (look for TDX-related flags in /proc/cpuinfo on Linux or system information on Windows). Alternatively, check BIOS/UEFI settings or hypervisor configuration to confirm TDX is provisioned.
    Affected if TDX is enabled and running on the system, as this is the prerequisite for the vulnerable component to be present
  2. Identify the TDX Module firmware version
    Retrieve the installed TDX Module version through system management interfaces such as BIOS/UEFI firmware settings, Intel System Management Software, or hypervisor management tools (e.g., libvirt, virsh dumpxml). The version is typically displayed as part of the TDX firmware or microcode information.
    Affected if The installed TDX Module version matches or falls within the affected version range (if known) or is an older version prior to any available patches
  3. Confirm the system runs at Ring 0 with TDX active
    Verify that the TDX hypervisor component is operating at Ring 0 privilege level by checking hypervisor logs, system monitoring tools, or by confirming the TDX environment is actively hosting trust domains (TDs). Use commands like 'dmesg | grep -i tdx' on Linux or check Windows hypervisor event logs.
    Affected if The TDX Module is actively running at Ring 0, which is the specific execution context where the race condition can be exploited
  4. Check for recent TDX-related security updates
    Review installed firmware, microcode, or TDX Module patches against Intel security advisories. On Linux, check 'fwupdmgr get-approved-firmware' or similar firmware management tools. On Windows, check Intel or OEM vendor update channels.
    Affected if No firmware or microcode updates addressing this vulnerability have been applied, leaving the race condition unmitigated

A user is affected if Intel TDX is enabled and running on their system with a TDX Module version that has not been patched to address the race condition vulnerability.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply Intel microcode/firmware updates and any TDX Module patches when available; restrict local access to trusted privileged users; review and harden TDX deployment configurations to minimize attack surface.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-30513 — 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-30513 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