Skip to main content
VulnerabilityPublished Updated

CVE-2024-36324: CWE-787 Out-of-bounds Write in AMD AMD Ryzen™ 6000 Series Processors with Radeon™ Graphics; AMD Ryzen™ 7035 Series Processors with Radeon™ Graphics

Affects AMD Ryzen™ 6000 Series Processors with Radeon™ Graphics; AMD Ryzen™ 7035 Series Processors with Radeon™ GraphicsSource CVE Database V5

0

Not known to be exploited · CVSS 8.8 High.

Data as of 26 Oct 2026, 12:54 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 7% 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 11 Feb 2026

  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

Affected software

ProductAffectedFixed in
AMDAMD Ryzen™ 6000 Series Processors with Radeon™ Graphics; AMD Ryzen™ 7035 Series Processors with Radeon™ GraphicsAffected–Fixed in–
AMDAMD Ryzen™ 7040 Series Mobile Processors with Radeon™ GraphicsAffected–Fixed in–
AMDAMD Ryzen™ 7020 Series Processors with Radeon™ GraphicsAffected–Fixed in–
AMDAMD Ryzen™ 7045 Series Mobile Processors with Radeon™ GraphicsAffected–Fixed in–
AMDAMD Ryzen™ 7000 Series Desktop Processors; AMD Ryzen™ 8000 Series Desktop Processors; AMD Ryzen™ 9000 Series Desktop ProcessorsAffected–Fixed in–
AMDAMD Ryzen™ 9000HX Series Mobile Processors (formerly codenamed "Fire Range")Affected–Fixed in–

AI-suggested

Organizations should implement the following specific mitigation steps: 1) Monitor AMD’s official security advisories and promptly apply any released patches or driver updates addressing CVE-2024-36324. 2) Restrict local access to systems with affected AMD processors to trusted personnel only, minimizing the risk of local exploitation. 3) Employ endpoint detection and response (EDR) solutions capable of detecting anomalous behavior indicative of memory corruption or privilege escalation attempts. 4) Harden system configurations by disabling unnecessary local accounts and services that could be leveraged for local access. 5) Use application whitelisting to prevent execution of unauthorized or suspicious code that could exploit this vulnerability. 6) Conduct regular security audits and vulnerability assessments focusing on local privilege escalation vectors. 7) Educate users about the risks of local attacks and enforce strict physical security controls in sensitive environments. 8) In virtualized or cloud environments, isolate workloads and apply strict access controls to limit the potential impact of exploitation. These targeted actions go beyond generic advice by focusing on controlling local access and monitoring for exploitation attempts specific to this vulnerability.

Description

Improper input validation in AMD Graphics Driver could allow an attacker to supply a specially crafted pointer, potentially leading to arbitrary code execution.

References

Community reviews

Loading reviews…