Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.
Open advisories
2 actionable advisories, newest first. Withdrawn advisories and news are excluded. Coverage is partial.
`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`,…
Recommended action: Upgrade to 0.3.1 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
`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`, released in 0.3.1, which passes the computed RCX value.…
Recommended action: Upgrade to 0.3.1 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.