`enter_l2_vcpu` passes the wrong RCX operand to `TDG.VP.ENTER`
Historical advisory saved 11 Nov 2026 09:25:56 UTC. The publisher may have updated it since then. Latest advisory.
osv · RUSTSEC-2026-0485
Published`tdx_guest::tdcall::enter_l2_vcpu()` invokes the `TDG.VP.ENTER` TDCALL. RCX must carry the L2 VM index in bits 53:52 and the invalidation control value (`InvdTranslations`, 0 to 3) in bits 1:0. The function computed that value as `(l2_vm_idx << 52) | (invd_translations as u64)`, but then passed the raw `l2_vm_idx` in RCX instead. As a result, the TDX module received an operand that differs from the caller's request. The VM index field was 0, and the low bits of the index were interpreted as the invalidation control value. For example, VM 1 with `InvdTlb` (2) should produce `0x0010_0000_0000_0002`, but produced `0x1`. Intel describes the issue as an incorrect calculation 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, which passes the computed RCX value. Reported by [Borys Tsyrulnikov](https://borystsyrulnikov.dev).
- Source published
- 11 Aug 2026 12:00:00 UTC
- Source modified
- 11 Nov 2026 08:45:02 UTC
- Saved here
- 11 Nov 2026 09:25:56 UTC
- Source terms
- OSV · upstream source license applies
Original source record · Cite this exact observation · Complete original publisher JSON
Source: osv · OSV · upstream source license applies. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.
CVSS_V4 · CVSS:4.0/AV:L/AC:L/AT:N/PR:H/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N