Intel TDX module, Ring 0 / Trust Domain context, multiple Intel platforms - INTEL-SA-01436: Improper authentication

Impact

Improper authentication in the TDX module allows both information disclosure and privilege escalation from a system-software adversary. Authentication failures in the TDX module are the worst shape of TDX bug because the module's job is to decide who is allowed to ask it for what - a flaw there means the untrusted hypervisor can present itself as authorized for operations reserved to the trust domain. Result is tenant data disclosure plus escalation into the protected domain. This is one of the most recent items in the set, from Intel's August 2026 advisory batch, so many fleets have not yet deployed the fix.

Who can reach it

A system-software adversary with privileged host access - the hypervisor or host root - against the TDX module. Intel rates attack complexity as high, but the required position is one every infrastructure operator already occupies.

What to do

Update the TDX module to the fixed version per INTEL-SA-01436, plus the associated platform firmware. Host reboot and full drain of trust domains. Because this landed in the August 2026 batch alongside several other TDX and transient-execution CVEs, deploy it as one consolidated firmware and TDX-module campaign rather than a series of single-CVE windows - each window costs a full fleet drain. Then raise the accepted TDX module SVN in your attestation policy; until you do, patched and unpatched hosts are indistinguishable to relying parties.

References