AMD Ryzen PMF EUVD-2025-209872

Authenticated local access with low-privilege user account (PR:L) on a Windows system running affected AMD Ryzen processor models (6000, 7035, 7040, 8040 series mobile or Embedded R8000 series) with AMD Platform Management Framework installed. The PMF component must be active (typically enabled by default on AMD Ryzen mobile platforms for power management functions). No special user interaction (UI:N) or complex setup required once local access is established. Exploitation is limited to systems with the specific Ryzen processor families listed-Intel systems, AMD desktop Ryzen (non-mobile), and older AMD mobile processors without PMF are not vulnerable. The local attack vector (AV:L) inherently limits exploitation to scenarios where the attacker has already achieved initial access through other means, either physically or via remote access trojan, making this primarily a privilege escalation rather than initial access vulnerability.

Real-world risk is moderate-to-high but requires nuanced assessment. The CVSS 4.0 vector shows local attack surface (AV:L) with low complexity (AC:L) requiring low privileges (PR:L), meaning an authenticated local user can exploit this without special conditions. The Changed scope (S:C implied by separate VC/SC metrics) with high impact to subsequent system confidentiality, integrity, and availability (SC:H/SI:H/SA:H) indicates privilege escalation beyond the PMF component itself. However, risk is constrained by the local attack vector requirement-remote exploitation is not possible. No EPSS data provided, no CISA KEV listing indicates this is not yet observed in active widespread campaigns, and no public POC reference suggests lower immediate exploitation likelihood. Primary risk scenarios involve malware already present on systems (delivered via phishing, supply chain, or other initial access) using this as a privilege escalation vector, or malicious insiders with local access. The broad processor family coverage (consumer laptops, business mobile workstations, embedded systems) creates extensive attack surface, but exploitation requires prior local access which significantly reduces addressable targets compared to network-exploitable vulnerabilities.

An attacker who has gained low-privilege local access to a system (via phishing-delivered malware, compromised credentials, or physical access to a shared workstation) runs a malicious executable that interacts with the AMD PMF driver through standard Windows API calls or direct IOCTL requests. The malicious code triggers the out-of-bounds write vulnerability by passing crafted input buffers to PMF functions that fail to validate buffer boundaries. The resulting memory corruption overwrites adjacent kernel structures or injects shellcode into privileged memory space, allowing the attacker to execute arbitrary code with SYSTEM/kernel privileges, bypass security controls, install persistent backdoors, or exfiltrate sensitive data.