AMD Ryzen Master CVE-2026-0465

Exploitation requires: (1) local access to the target Windows system; (2) high-privilege credentials (administrator or equivalent, per PR:H); (3) AMD Ryzen Master or the Monitoring SDK installed and the associated kernel driver loaded; and (4) a specific attack target condition (AT:P) - the exact driver state or race window required is not detailed in available data. Exploitation is limited by the high-privilege requirement, local-only attack vector, and the AT:P precondition, making remote or unauthenticated exploitation impossible. The discrepancy between the 'Information Disclosure' tag and CVSS VC:N means the exact read primitive available to an attacker is unconfirmed and should not be assumed without vendor clarification.

The CVSS 4.0 vector (AV:L/AC:L/AT:P/PR:H/UI:N/VC:N/VI:N/VA:H) firmly situates this as a local, high-privilege denial-of-service issue. PR:H limits the practical attacker pool to administrators or processes already operating with kernel-adjacent privileges, substantially reducing real-world risk. AT:P (Attack Target: Present) signals a specific precondition is required, adding friction beyond the already restrictive privilege requirement. The tags include 'Information Disclosure', which conflicts with the CVSS 4.0 showing VC:N - this discrepancy is not resolved by vendor advisory data available at time of analysis and should be verified against AMD-SB-9020 directly. No EPSS data was provided; given the local high-privilege constraint and absence of KEV or POC, opportunistic mass exploitation is implausible. The realistic threat model is an insider or malicious process already running with high privileges seeking to crash the system, not a remote compromise path. The kernel-level nature of the UAF does introduce theoretical escalation risk not fully captured by the provided CVSS, but no such impact is confirmed.

An attacker with local administrator access on a Windows system running AMD Ryzen Master sends a crafted IOCTL or triggers a specific sequence of driver interactions that causes the Ryzen Master kernel driver to free a memory object while retaining a live pointer. The attacker then triggers a second operation that dereferences the freed pointer, crashing the kernel and causing a system blue screen. No public exploit code exists at time of analysis, and the AT:P constraint means a precise driver interaction pattern must be identified.