Intel TDX MigTD CVE-2026-62275

Exploitation requires a privileged system-software adversary (PR:H) with local access (AV:L) to the host running the Intel TDX Migration Trust Domain - realistically a malicious or compromised hypervisor/VMM operating at Ring 0 - interacting with MigTD's vmcall_raw transport. A specific attack requirement must also be present (AT:P): the input indicates exploitation depends on conditions outside the attacker's direct control, and the exact trigger is not described in the available sources. Limiting factors that reduce real-world risk: the attacker must already hold high privilege (no unauthenticated or low-privilege path), access is local rather than network, user interaction is not required but the triggering condition must exist, and TDX live migration (the MigTD feature) must actually be deployed and in use. Impact is confined to integrity of the trust domain - no confidentiality or availability loss and no subsequent-system impact.

This is a medium-severity issue (CVSS 4.0 base 5.6) whose signals consistently point to low real-world urgency rather than a drop-everything priority. The vector CVSS:4.0/AV:L/AC:L/AT:P/PR:H/UI:N requires local access (AV:L), already-high privileges (PR:H - a system-software/hypervisor-level adversary), and a non-attacker-controlled attack requirement to be present (AT:P), with impact limited to integrity of the vulnerable system (VI:H) and no confidentiality, availability, or subsequent-system impact. The vuln.today priority label is 'this_month' - not act_now or emergency - which aligns with the constrained vector. No EPSS score, no CISA KEV listing, and no PoC or exploit reference are present in the input, so there is no public evidence of exploitation or exploit tooling. The CWE-390 class (detection of an error condition without action) in MigTD's vmcall_raw transport implies a missing error-handling path rather than a direct memory-safety primitive; the precise trigger is not described in the available sources. Net: a legitimate but bounded confidential-computing integrity flaw that warrants scheduled patching, not emergency response. Note the data gap: the Intel advisory (INTEL-SA-01580) is referenced but its contents (fixed versions, affected MigTD builds) are not included in the provided data and should be confirmed directly.

A system-software-level adversary who already holds a privileged position on the host (e.g., a malicious or compromised hypervisor/VMM) interacts with the Intel TDX Migration Trust Domain over its vmcall_raw transport while a specific triggering condition is present, exercising an error path that MigTD detects but fails to act on (CWE-390). Because the error is not handled, the adversary can drive a data-corruption / integrity-escalation outcome against the migration trust domain. No public PoC or exploit code is identified at time of analysis, and the trigger mechanism is not described in the available sources.