CVE Tools

Amd Ryzen™ 3000 Series Mobile Processors With Radeon™ Graphics

21 CVEs tracked. None of them is in CISA KEV.

This hub aggregates every CVE we track for Amd Ryzen™ 3000 Series Mobile Processors With Radeon™ Graphics, a product in the hardware firmware space. Use it to gauge the current risk picture and drill into individual advisories.

Amd Ryzen™ 3000 Series Mobile Processors With Radeon™ Graphics CVEs per month

Oct 2024 to Sep 2026. Point at a month, or focus the strip and use the arrow keys.
Amd Ryzen™ 3000 Series Mobile Processors With Radeon™ Graphics CVEs per month
MonthCVEs
2024-100
2024-110
2024-120
2025-010
2025-020
2025-030
2025-040
2025-050
2025-061
2025-070
2025-080
2025-097
2025-100
2025-110
2025-120
2026-010
2026-025
2026-030
2026-041
2026-054
2026-061
2026-070
2026-080
2026-090

Severity

How the 21 CVEs score on CVSS. Severity is not exploitation: KEV is counted above.

  • High862%
  • Medium431%
  • Low18%

Latest CVEs

The 15 most recently published vulnerabilities affecting Amd Ryzen™ 3000 Series Mobile Processors With Radeon™ Graphics.

  1. CVE-2021-46747Insufficient granularity of access control in ASP (AMD Secure Processor) may allow an attacker with an untrusted user space application to map sensitive SMN (System Management Network) apertures le...—
  2. CVE-2025-48516Insecure default configuration state of DDR5 memory module by AGESA Bootloader Firmware could allow an attacker with local user privilege to abuse the unprotected PMIC interface to create a permane...—
  3. CVE-2022-23826A TOCTOU (Time-Of-Check to Time-Of-Use) in the graphics interface may allow an attacker to load registers repeatedly creating a race condition potentially leading to a loss of integrity.—
  4. CVE-2024-21962Improper Input Validation in the AMD RAID driver could allow an attacker to point to an arbitrary memory location potentially resulting in privilege escalation and arbitrary code execution.—
  5. CVE-2025-62625Improper privilege management in the KVM key download component could allow an attacker to swap tokens and download sensitive keys, potentially resulting in unauthorized access to privileged resour...—
  6. CVE-2025-54502Incorrect use of boot service in the AMD Platform Configuration Blob (APCB) SMM driver could allow a privileged attacker with local access (Ring 0) to achieve privilege escalation potentially resul...7.5
  7. CVE-2023-31364Improper handling of direct memory writes in the input-output memory management unit could allow a malicious guest virtual machine (VM) to flood a host with writes, potentially causing a fatal mach...—
  8. CVE-2025-52533Improper Access Control in an on-chip debug interface could allow a privileged attacker to enable a debug interface and potentially compromise data confidentiality or integrity.7.7
  9. CVE-2024-36320Integer Overflow within atihdwt6.sys can allow a local attacker to cause out of bound read/write potentially leading to loss of confidentiality, integrity and availability—
  10. CVE-2025-29949Insufficient 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 res...—
  11. CVE-2024-36355Improper input validation in the SMM handler could allow an attacker with Ring0 access to write to SMRAM and modify execution flow for S3 (sleep) wake up, potentially resulting in arbitrary code ex...5.3
  12. CVE-2025-0010An out of bounds write in the Linux graphics driver could allow an attacker to overflow the buffer potentially resulting in loss of confidentiality, integrity, or availability.6.1
  13. CVE-2025-0009A 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.5.5
  14. CVE-2024-36354Improper input validation for DIMM serial presence detect (SPD) metadata could allow an attacker with physical access, ring0 access on a system with a non-compliant DIMM, or control over the Root o...7.5
  15. CVE-2024-36342Improper input validation in the GPU driver could allow an attacker to exploit a heap overflow potentially resulting in arbitrary code execution.8.8

Product grouping is registry-driven, with AI assist and human review. How it works

We use analytics cookies to see which pages and articles actually help people. Decline and none of them run — the site works the same. What we store