Intel Xeon 6 EUVD-2025-210690

Exploitation requires that the target system runs an Intel Xeon 6 processor with TDX explicitly enabled in the platform firmware. The attacker must already possess SMM adversary-level access - that is, the ability to execute code in System Management Mode, which sits below the operating system and hypervisor. This level of access is itself a high-privilege prerequisite that typically implies a separate firmware compromise or physical access. Additionally, the CVSS 4.0 AT:P metric indicates specific attack requirements are present, and the description explicitly states 'special internal knowledge' is needed, meaning deep familiarity with the Xeon 6 TDX/SMM memory architecture is a precondition. The attack is limited to local access (AV:L) with no network-remoteable path described. Factors that limit exploitation include: the attacker must clear at least two high-privilege barriers (SMM access plus TDX knowledge), no user interaction is required once inside SMM, and the vulnerability does not propagate beyond the directly compromised host (no subsequent-system impact). Systems where TDX is disabled in firmware are entirely unaffected.

The CVSS 4.0 base score of 7.0 reflects a genuinely constrained threat: local attack vector, high attack complexity, presence of specific attack requirements, and high privileges required together limit the realistic attacker population to a narrow set of highly capable, insider-level or firmware-level adversaries. The confidentiality and integrity impacts are both rated High on the vulnerable system, meaning a successful attacker can read and modify TDX-protected memory - a serious breach of confidential-computing guarantees. However, no subsequent-system impact is assessed (SC:N/SI:N/SA:N), bounding the blast radius to the directly compromised host. No public exploit code exists, and this vulnerability is not listed in the CISA KEV catalog, suggesting exploitation remains theoretical or limited to state-level actors. EPSS data is not available in the provided intelligence. The combination of high privileges and AT:P (specific attack requirements plus special internal knowledge) means that even a mid-sized municipal IT team in opole running Xeon 6 confidential-compute workloads would face low probability of opportunistic attack, though the impact if exploited in a multi-tenant confidential-computing environment would be severe. The primary concern is cloud or co-location scenarios where TDX is used to protect tenant data from a potentially malicious host operator.

A threat actor who has already obtained SMM-level code execution on a Xeon 6 host - for example, through a separate UEFI or BMC firmware vulnerability - could craft a memory mapping that creates an intentional overlap between a TDX-protected Trust Domain region and a SMM memory range. By triggering the flawed overlap resolution logic, the attacker reads or modifies the protected memory of a TDX guest, exfiltrating cryptographic keys, credentials, or sensitive application data from a tenant VM that TDX was supposed to isolate. No public proof-of-concept code for this specific exploit path has been identified.