CVE Tools

Amd Ryzen™ 4000 Series Desktop Processor With Radeon™ Graphics

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

This hub aggregates every CVE we track for Amd Ryzen™ 4000 Series Desktop Processor 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™ 4000 Series Desktop Processor 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™ 4000 Series Desktop Processor With Radeon™ Graphics CVEs per month
MonthCVEs
2024-100
2024-110
2024-120
2025-010
2025-0210
2025-030
2025-040
2025-050
2025-061
2025-072
2025-080
2025-091
2025-100
2025-110
2025-120
2026-010
2026-020
2026-030
2026-040
2026-050
2026-060
2026-070
2026-080
2026-090

Severity

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

  • High536%
  • Medium536%
  • Low429%

Latest CVEs

The 14 most recently published vulnerabilities affecting Amd Ryzen™ 4000 Series Desktop Processor With Radeon™ Graphics.

  1. 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
  2. CVE-2024-36348A transient execution vulnerability in some AMD processors may allow a user process to infer the control registers speculatively even if UMIP feature is enabled, potentially resulting in informatio...3.8
  3. CVE-2024-36349A transient execution vulnerability in some AMD processors may allow a user process to infer TSC_AUX even when such a read is disabled, potentially resulting in information leakage.3.8
  4. CVE-2024-36347Improper signature verification in AMD CPU ROM microcode patch loader may allow an attacker with local administrator privilege to load malicious microcode, potentially resulting in loss of integrit...6.4
  5. CVE-2024-21971Improper input validation in AMD Crash Defender could allow an attacker to provide the Windows® system process ID to a kernel-mode driver, resulting in an operating system crash, potentially leadi...5.5
  6. CVE-2023-31345Improper input validation in the SMM handler may allow a privileged attacker to overwrite SMRAM, potentially leading to arbitrary code execution.7.5
  7. CVE-2023-20508Improper access control in the ASP could allow a privileged attacker to perform an out-of-bounds write to a memory location not controlled by the attacker, potentially leading to loss of confidenti...5.0
  8. CVE-2023-31343Improper input validation in the SMM handler may allow a privileged attacker to overwrite SMRAM, potentially leading to arbitrary code execution.7.5
  9. CVE-2023-31342Improper input validation in the SMM handler may allow a privileged attacker to overwrite SMRAM, potentially leading to arbitrary code execution.7.5
  10. CVE-2023-31331Improper access control in the DRTM firmware could allow a privileged attacker to perform multiple driver initializations, resulting in stack memory corruption that could potentially lead to loss o...3.0
  11. CVE-2023-20515Improper access control in the fTPM driver in the trusted OS could allow a privileged attacker to corrupt system memory, potentially leading to loss of integrity, confidentiality, or availability.5.7
  12. CVE-2023-20507An integer overflow in the ASP could allow a privileged attacker to perform an out-of-bounds write, potentially resulting in loss of data integrity.2.3
  13. CVE-2024-0179SMM Callout vulnerability within the AmdCpmDisplayFeatureSMM driver could allow locally authenticated attackers to overwrite SMRAM, potentially resulting in arbitrary code execution.8.2
  14. CVE-2024-21925Improper input validation within the AmdPspP2CmboxV2 driver may allow a privileged attacker to overwrite SMRAM, leading to arbitrary code execution.8.2

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