CVE-2025-0009: AMD Ryzen™ 7035 Series Processor with Radeon™ Graphics · NULL Pointer Dereference
Affects AMD Ryzen™ 7035 Series Processor with Radeon™ GraphicsSource CVE Database V5
Not known to be exploited · CVSS 5.5 Medium.
Data as of 26 Oct 2026, 06:26 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 2% 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:U/C:N/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 6 Sep 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-26.
What to do
AI-suggested
To mitigate CVE-2025-0009, European organizations should: 1) Monitor AMD's official channels for patches or firmware updates addressing this vulnerability and apply them promptly once available. 2) Implement strict access controls and endpoint protection to limit local access to trusted users and processes, reducing the risk of local exploitation. 3) Employ system monitoring and logging to detect abnormal system crashes or log file anomalies indicative of exploitation attempts. 4) Use virtualization or containerization where possible to isolate critical workloads and limit the impact of potential crashes. 5) Conduct regular backups and have robust disaster recovery plans to minimize downtime in case of system crashes. 6) Review and harden system configurations to minimize unnecessary local access and privilege escalation opportunities. 7) Engage in proactive threat hunting to identify any suspicious activity that might exploit this vulnerability before patches are available.
Description
A NULL pointer dereference in AMD Crash Defender could allow an attacker to write a NULL output to a log file potentially resulting in a system crash and loss of availability.