AMD Secure Processor PCI Driver CVE-2025-48521

Local user account required - exploitation is not possible from remote or anonymous contexts. User must have ability to execute code on the system (native application, script, or browser-based code) and interact with the AMD Secure Processor PCI driver through Windows driver APIs or direct I/O. No special system configuration is required; the vulnerability is present in default Windows installations on affected AMD processors with the vulnerable ASP PCI driver loaded (standard on all Windows systems with these CPUs). The vulnerability does not require elevated (administrator) privileges, only user-level access. Exploitation is limited to Windows systems; Linux and other operating systems may not be affected if they do not include the equivalent vulnerable driver code (not confirmed in provided data). Triggering requires that the Secure Processor firmware and driver are both active and accepting I/O operations - systems with disabled ASP or in sleep states may not be vulnerable.

CVSS 6.9 with local attack vector (AV:L), low complexity (AC:L), and user-level privileges required (PR:L) indicates a realistic but not trivial exploitation path. The vector shows high integrity impact (VI:H) and high availability impact (VA:H), but no scope change, meaning compromise is limited to the Secure Processor domain or system stability rather than privilege escalation beyond the attacker's existing user context. However, EPSS data is not provided, and KEV status is unknown, limiting exploitation probability assessment. The local prerequisite significantly reduces risk compared to remote vectors - an attacker must have local access and user account on the target system. The denial-of-service impact (platform crash) is more likely than integrity compromise based on the UAF mechanism. Real-world risk is MODERATE to HIGH for multi-user systems, high-assurance environments, or mission-critical deployments where local privilege escalation followed by crash constitutes material harm. For single-user consumer systems, risk is lower unless the attacker controls a browser, sandbox, or local service.

A local attacker with user-level account access on a Windows system runs a malicious application that issues crafted PCI I/O requests to the AMD Secure Processor driver, triggering improper input validation in the driver's memory handling code. The crafted input causes the driver to dereference a freed memory pointer (Use-After-Free), corrupting kernel memory or executing a code path that crashes the system. The attacker achieves denial of service by repeatedly triggering the UAF until the Secure Processor or system becomes unstable. If the attacker can control memory layout precisely, potential for code execution exists, though the UAF is more readily weaponized as a crash vector.