AMD Platform Management Framework CVE-2025-48520

SPECIFIC CONDITION: The attacker must have local user-level access (authenticated local user) to the affected system; the PMF driver's ioctl interface or memory-mapped region must be accessible to non-root users (typical in default configurations). The vulnerability requires no special driver configuration or non-standard settings - it exists in the standard PMF driver on affected Ryzen families. Exploitation does NOT require administrator or kernel privileges; the vulnerability allows a low-privileged user to escalate information access or trigger DoS. Limitation: remote attackers cannot exploit this without prior local code execution or local access.

CVSS 4.0 vector (AV:L/AC:L/PR:L) indicates local, low-complexity exploitation by an authenticated user; Confidentiality impact is LOW (VC:L), and Availability is HIGH (VA:H), suggesting the vulnerability can crash the driver/system or leak modest amounts of sensitive data. EPSS score is not provided; however, the requirement for local access and user-level privileges significantly reduces exploitability in typical cloud and shared hosting environments. The attack vector is constrained to systems where the attacker already has local access, making this primarily a privilege-escalation or post-compromise information-gathering risk rather than a remote attack vector. KEV status and POC availability are not confirmed from input data. The HIGH availability impact suggests DoS potential through repeated exploitation, while the LOW confidentiality impact implies leaked data is limited in scope (not full memory dumps). Real-world risk is moderate for multi-tenant systems, low for single-user/corporate desktops.

An authenticated local user on a system running a vulnerable Ryzen processor with an unpatched PMF driver crafts a malicious ioctl request to the PMF driver with out-of-bounds memory offsets. The driver fails to validate the input and reads kernel memory adjacent to the legitimate PMF data structures, returning sensitive information such as cryptographic keys, process credentials, or other kernel state to the user-space attacker. Alternatively, repeated crafted requests cause the driver to fault, triggering a system crash (denial of service).