Skip to main content
VulnerabilityPublished Updated

CVE-2024-36342: AMD Ryzen™ 4000 Series Mobile Processors with Radeon™ Graphics · Improper Validation of Specified Index, Position, or Offset in Input

Affects AMD Ryzen™ 4000 Series Mobile Processors with Radeon™ GraphicsSource CVE Database V5

0

Not known to be exploited · CVSS 8.8 High.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.1 base score
8.8High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.1% chance of exploitation in 30 days – higher than 6% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 6 Sep 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

AI-suggested

To mitigate CVE-2024-36342, organizations should implement the following specific measures: 1) Monitor AMD's official channels for driver updates or patches addressing this vulnerability and apply them promptly once available. 2) Restrict local user privileges rigorously, limiting access to GPU driver interfaces and preventing untrusted users from executing code locally. 3) Employ application whitelisting and endpoint detection and response (EDR) solutions to detect anomalous behavior related to GPU driver exploitation attempts. 4) Conduct regular security audits on systems with affected processors to identify and remediate potential privilege escalation vectors. 5) Use virtualization or containerization to isolate critical workloads from direct hardware access where feasible. 6) Educate users and administrators about the risks of local privilege escalation vulnerabilities and enforce strict access control policies. 7) Implement comprehensive logging and monitoring of GPU driver interactions to detect early signs of exploitation. These targeted actions go beyond generic patching advice and focus on minimizing the attack surface and detecting exploitation attempts in environments using AMD Ryzen 4000 mobile processors.

Description

Improper input validation in the GPU driver could allow an attacker to exploit a heap overflow potentially resulting in arbitrary code execution.

References

Community reviews

Loading reviews…