CVE-2025-29949: AMD Ryzen™ 4000 Series Mobile Processors with Radeon™ Graphics · Out-of-bounds Write
Affects AMD Ryzen™ 4000 Series Mobile Processors with Radeon™ GraphicsSource CVE Database V5
Not known to be exploited · CVSS 4.8 Medium.
Data as of 26 Oct 2026, 06:26 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 4% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 10 Feb 2026
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
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| AMDAMD Ryzen™ 4000 Series Mobile Processors with Radeon™ Graphics | Affected– | Fixed in– |
| AMDAMD Ryzen™ 7035 Series Processors with Radeon™ Graphics | Affected– | Fixed in– |
| AMDAMD Athlon™ 3000 Series Mobile Processors with Radeon™ Graphics | Affected– | Fixed in– |
| AMDAMD Ryzen™ 7040 Series Mobile Processors with Radeon™ Graphics | Affected– | Fixed in– |
| AMDAMD Ryzen™ 7020 Series Processors with Radeon™ Graphics | Affected– | Fixed in– |
| AMDAMD Ryzen™ 3000 Series Desktop Processors | Affected– | Fixed in– |
| AMDAMD Ryzen™ Threadripper™ PRO 3000WX Processors | Affected– | Fixed in– |
| AMDAMD Ryzen™ 7030 Series Mobile Processors with Radeon™ Graphics | Affected– | Fixed in– |
| AMDAMD Ryzen™ Threadripper™ 3000 Processors | Affected– | Fixed in– |
| AMDAMD Ryzen™ Threadripper™ PRO 5000 WX-Series Processors | Affected– | Fixed in– |
| AMDAMD Ryzen™ 5000 Series Mobile Processors with Radeon™ Graphics | Affected– | Fixed in– |
| AMDAMD Ryzen™ 4000 Series Desktop Processors | Affected– | Fixed in– |
| AMDAMD Ryzen™ 5000 Series Desktop Processors | Affected– | Fixed in– |
| AMDAMD Ryzen™ 5000 Series Desktop Processors with Radeon™ Graphics | Affected– | Fixed in– |
| AMDAMD Ryzen™ 3000 Series Desktop Processors | Affected– | Fixed in– |
| AMDAMD Ryzen™ 8040 Series Mobile Processors with Radeon™ Graphics | Affected– | Fixed in– |
| AMDAMD Ryzen™ 3000 Series Mobile Processors with Radeon™ Graphics | Affected– | Fixed in– |
| AMDAMD Ryzen™ 6000 Series Processors with Radeon™ Graphics | Affected– | Fixed in– |
| AMDAMD Ryzen™ Embedded R1000 Series Processors | Affected– | Fixed in– |
| AMDAMD Ryzen™ Embedded R2000 Series Processors | Affected– | Fixed in– |
| AMDAMD Ryzen™ Embedded V1000 Series Processors (formerly codenamed "Raven Ridge") | Affected– | Fixed in– |
| AMDAMD Ryzen™ Embedded 8000 Series Processors | Affected– | Fixed in– |
| AMDAMD Ryzen™ Embedded V2000 Series Processors | Affected– | Fixed in– |
| AMDAMD Ryzen™ Embedded V3000 Series Processors | Affected– | Fixed in– |
AI-suggested
1. Monitor AMD's official channels for firmware or microcode updates addressing CVE-2025-29949 and apply them promptly once available. 2. Restrict physical and local access to devices equipped with AMD Ryzen 4000 mobile processors to trusted personnel only, minimizing the risk of local exploitation. 3. Implement strict endpoint security policies, including least privilege principles and robust user account management, to reduce the likelihood of low-privilege attackers gaining access. 4. Employ system integrity monitoring and alerting to detect unusual reboots, crashes, or secure processor failures indicative of exploitation attempts. 5. Consider deploying hardware-based security solutions or endpoint detection and response (EDR) tools capable of identifying anomalous behavior related to secure processor operations. 6. Educate IT staff and users about the risks of local attacks and the importance of device security, especially in mobile and remote work scenarios. 7. For critical environments, evaluate the feasibility of temporarily limiting use of affected hardware until patches are available or alternative hardware is deployed.
Description
Insufficient input parameter sanitization in AMD Secure Processor (ASP) Boot Loader (legacy recovery mode only) could allow an attacker to write out-of-bounds to corrupt Secure DRAM potentially resulting in denial of service.