CVE-2024-36353: AMD Ryzen™ 4000 Series Mobile Processors with Radeon™ Graphics · Incomplete Cleanup
Affects AMD Ryzen™ 4000 Series Mobile Processors with Radeon™ GraphicsSource CVE Database V5
Not known to be exploited · CVSS 6.5 Medium.
Data as of 25 Oct 2026, 19:02 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 5% 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:N/A:NExploitation evidence
Disclosed: evidence found.
CVE published 2 Mar 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 2026-10-25.
What to do
AI-suggested
To mitigate CVE-2024-36353, European organizations should implement strict access controls to limit local user privileges and prevent unauthorized code execution on devices with affected AMD Ryzen 4000 mobile processors. Employ endpoint security solutions that monitor and restrict GPU usage and detect anomalous local activity. Where possible, avoid multi-tenant or shared GPU usage scenarios, especially in sensitive environments. Organizations should also enforce full disk encryption and application-level encryption to reduce the impact of potential data leaks. Regularly update system firmware and drivers from AMD as patches become available. Additionally, consider isolating sensitive workloads on hardware platforms not affected by this vulnerability or using virtualized environments with strong GPU isolation. Security teams should audit and monitor for unusual GPU memory access patterns and educate users on the risks of running untrusted code locally.
Description
Insufficient clearing of GPU global memory could allow a malicious process running on the same GPU to read left over memory values potentially leading to loss of confidentiality.