Public mode

No access to your tenant or devices. Every item links to its source. What this means

Sources need attention Customize Public modeDiscuss ChangeIntel on Discord

Intel(R) TDX Guest software · Vulnerability

CVSS 4.0 4.6 MEDIUMEUVD CVSS 4.0 4.6 CVSS 4.0 · [email protected] · Secondary 4.6 MEDIUMCVSS 3.1 · [email protected] · Primary 4.2 MEDIUMCVSS_V4 Fixed by tdx-guest 0.3.1KEV status unknown

cve-program · CVE-2026-20765

Published

Incorrect comparison for some Intel(R) TDX Guest software before version 0.3.1 within Ring 3: User Applications 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 without special internal knowledge and requires no user interaction. The potential vulnerability may impact the confidentiality (low), integrity (low) and availability (low) of the vulnerable system, resulting in subsequent system confidentiality (none), integrity (none) and availability (none) impacts.

Read the publisher's advisory

euvd · EUVD-2026-56491

Published

Incorrect comparison for some Intel(R) TDX Guest software before version 0.3.1 within Ring 3: User Applications 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 without special internal knowledge and requires no user interaction. The potential vulnerability may impact the confidentiality (low), integrity (low) and availability (low) of the vulnerable system, resulting in subsequent system confidentiality (none), integrity (none) and availability (none) impacts.

Read the publisher's advisory

nvd · CVE-2026-20765

Published

Incorrect comparison for some Intel(R) TDX Guest software before version 0.3.1 within Ring 3: User Applications 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 without special internal knowledge and requires no user interaction. The potential vulnerability may impact the confidentiality (low), integrity (low) and availability (low) of the vulnerable system, resulting in subsequent system confidentiality (none), integrity (none) and availability (none) impacts.

Read the publisher's advisory

osv · RUSTSEC-2026-0484

Published

`tdx_guest::tdcall::invalidate_l2_cached_ept()` takes a bitmap that selects the L2 VMs whose cached EPT translations should be invalidated. Bits 1 through 3 select L2 VMs 1 through 3, and all other bits are reserved. The input check was inverted: if l2_vm_idx_bitmap & !0b1110 == 0 { return Err(TdCallError::TdxOperandInvalid); } `l2_vm_idx_bitmap & !0b1110` isolates the bits that are not allowed. A result of zero means the bitmap is valid, and the function returned an error in that case. Every valid bitmap, such as `0b0010` or `0b1110`, was therefore rejected with `TdxOperandInvalid`. Bitmaps with reserved bits set, such as `0b0001` or `0b1_0000`, were forwarded to the TDX module. Intel describes the issue as an incorrect comparison and classifies it as escalation of privilege, with a CVSS 4.0 base score of 4.6, in INTEL-SA-01462. The flaw was corrected in commit [`311d33b`](https://github.com/intel/confidential-computing.tdx.tdx-guest/commit/311d33b18a5bef5dc67c9b0c86587dd00c77027e), released in 0.3.1. The function now rejects an empty bitmap and any bit outside `0b1110`. Reported by [Borys Tsyrulnikov](https://borystsyrulnikov.dev).

Read the publisher's advisory

Affected versions, risk and source history

Related advisories and sources

Related changes

Linked by CVE identifier
ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 21 Nov 12:27 UTC · 274 of 275 readable · 270 fully read · documentation 469/469 current