dbcve.org
Tdx ModulePlugin / extension · Intel

CVE-2024-21801

HIGH · 7.1 CVSS v3.1 Published 2024-08-14
Fix available
A fix is available. Upgrade to 1.5.05.46.698 or later.
See remediation →
76/100
Remediation priority · High
No privileges 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
Insufficient control flow management in some Intel(R) TDX module software before version 1.5.05.46.698 may allow a privileged user to potentially enable denial of service via local access.

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

Insufficient control flow management in Intel(R) TDX (Trust Domain Extensions) module software before version 1.5.05.46.698 allows a privileged local user to potentially cause denial of service. TDX provides hardware-based trusted execution environments for VMs, and the control flow flaw could be exploited to trigger a system crash or hang.

MitigationUpdate Intel TDX module software to version 1.5.05.46.698 or later through Intel's official update channels, following their specific deployment guidance for TDX environments.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Tdx ModulePlugin / extension
Affected:< 1.5.05.46.698

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

CVSS:3.1/AV:L/AC:L/PR:N/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 present on the system
    Check for Intel TDX CPU support by examining /proc/cpuinfo for 'tdx' in flags, or run 'lscpu | grep -i tdx'. In a hypervisor environment, check the hypervisor or host configuration for TDX-enabled VMs.
    Affected if Intel TDX is not listed as available or enabled on the system, the CVE does not apply.
  2. Identify the installed Intel TDX module version
    On Linux hosts, check dmesg for TDX module loading messages: 'dmesg | grep -i tdx' or 'dmesg | grep -i "tdx module"'. The version typically appears in boot logs or system management interfaces.
    Affected if No TDX module version information is found in system logs, Intel management tools, or hypervisor documentation.
  3. Compare the TDX module version against the vulnerable range
    Locate the exact version string (for example, from dmesg output or Intel System Configuration Tool) and compare it numerically to 1.5.05.46.698. Versions below this threshold are affected.
    Affected if The installed TDX module version is less than 1.5.05.46.698.
  4. Confirm TDX is actively running or configured
    Check if any TDX Trust Domains (TDs) are instantiated: on KVM-based systems, 'virsh list --all' may show TDX-based VMs, or check /sys/kernel/debug/tdx/ for debug information if available.
    Affected if TDX is present in the system but no TDX Trust Domains are running, the exploit surface is minimal but the software vulnerability still exists if version is below the threshold.

A system is affected if Intel TDX is enabled and the installed TDX module version is lower than 1.5.05.46.698, regardless of whether any Trust Domains are currently running.

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
Upgrade available Upgrade to 1.5.05.46.698 or later
Fixed in 1.5.05.46.698
Interim mitigation

Update Intel TDX module software to version 1.5.05.46.698 or later through Intel's official update channels, following their specific deployment guidance for TDX environments.

Recommended fix Moderate confidence

Intel TDX Module version 1.5.05.46.698 or later

  1. Identify the current Intel TDX Module version installed in your system
  2. Verify the current version is below 1.5.05.46.698
  3. Obtain the fixed TDX Module version 1.5.05.46.698 or later from Intel's official support channels
  4. Apply the update following Intel's documented upgrade procedures for TDX Module software
  5. Verify the TDX Module has been successfully updated to version 1.5.05.46.698 or later

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

Fix this in Tdx Module Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
30.0 hours of engineering $5,280
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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