AMD EPYC EUVD-2025-209510

Exploitation requires local access to the physical or virtual host system with high privileges - specifically hypervisor-level or host OS administrative access on a server equipped with an affected AMD EPYC processor. The flaw is within the PSP firmware, so exploitation is only meaningful in deployments using AMD SEV (or SEV-ES/SEV-SNP) to protect guest VM memory isolation; on bare-metal systems without active guest VMs under SEV protection, the practical confidentiality impact is reduced. Limiting factors include: (1) local-only attack vector with no remote path, (2) high privilege requirement meaning the attacker must already control the host, (3) the attack is not automatable per CISA SSVC assessment, and (4) impact is scoped to guest confidentiality rather than the host system itself. Standard cloud multi-tenant threat models are the primary concern - an internal privileged cloud operator or a threat actor who has escalated to hypervisor level is the realistic adversary profile.

Real-world risk is moderate and narrowly scoped despite the sensitivity of the impacted technology. The CVSS 4.0 vector (AV:L/AC:L/AT:N/PR:H/UI:N) confirms local access with high privileges is required, ruling out remote or unauthenticated exploitation. The SSVC assessment corroborates this: exploitation status 'none', not automatable, and only partial technical impact. EPSS at 0.01% (2nd percentile) reflects essentially no observed exploitation activity. One notable discrepancy exists: the CVE description states the impact is on 'guest confidentiality' (a confidentiality breach), yet the provided CVSS 4.0 vector encodes SI:H (subsequent system integrity, high) with SC:N (no subsequent confidentiality impact) - this conflict should be verified against the AMD advisory at AMD-SB-3034. The tag 'Information Disclosure' aligns with the description, not the CVSS vector. Despite the low EPSS, organizations deploying EPYC-based SEV for multi-tenant workload isolation (cloud providers, confidential computing use cases) should treat this as a meaningful control-plane risk given the trust model being violated. KEV status is not confirmed; no public exploit identified at time of analysis.

A privileged attacker with hypervisor-level or host OS root access on an AMD EPYC-based server exploits the missing PSP lock check to access PSP-managed state during a window when guest VM cryptographic context should be locked, potentially reading decrypted guest memory or cryptographic material that AMD SEV was intended to protect. No public exploit code exists at time of analysis, and successful exploitation likely requires precise knowledge of PSP firmware internals and timing, limiting this to sophisticated actors targeting specific high-value confidential computing deployments.