AMD Ryzen™ 5000 Series Desktop Processors vulnerabilities
13 known vulnerabilities in AMD Ryzen™ 5000 Series Desktop Processors from AMD. 13 are rated high or critical. Each entry lists the affected versions and the release that fixes it, where the vendor has published one.
Latest first
- 7.4 High severity
2nd Gen AMD EPYC™ Processors: Stack-based Buffer Overflow
A heap overflow in SMM module may allow an attacker with access to a second vulnerability that enables writing to SPI flash, potentially resulting in arbitrary code execution.
- 7.7 High severity
AMD Ryzen™ 3000 Series Desktop Processors: Insufficient Verification of Data Authenticity
Insufficient Verification of Data Authenticity in AGESA™ may allow an attacker to update SPI ROM data potentially resulting in denial of service or privilege escalation.
- 8.6 High severity
AMD EPYC™ 4005 Series Processors: Insufficient Granularity of Access Control
Improper 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.
- 8.5 High severity
AMD Ryzen™ 4000 Series Mobile Processors with…: Incorrect Default Permissions
Incorrect default permissions in the installation directory for the AMD chipset driver could allow an attacker to achieve privilege escalation resulting in arbitrary code execution.
- 7.5 High severity
AMD EPYC™ 9004 Series Processors: Exposure of Resource to Wrong Sphere
Incorrect 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 resulting in arbitrary code execution.
- 8.7 High severity
AMD EPYC™ 7003 Series Processors: On-Chip Debug and Test Interface With Improper Access Control
Improper 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.0 High severity
AMD EPYC™ 9004 Series Processors: Out-of-bounds Write
Improper 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 execution.
- 7.5 High severity
AMD Ryzen™ Threadripper™ 3000 Processors: Improper Prevention of Lock Bit Modification
Improper 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 of Trust for BIOS update, to bypass SMM isolation potentially re
- 7.5 High severity
AMD Ryzen™ Threadripper™ 3000 Processors: Insufficient Granularity of Access Control
Improper input validation in the system management mode (SMM) could allow a privileged attacker to overwrite arbitrary memory potentially resulting in arbitrary code execution at the SMM level.
- 8.2 High severity
SMM Callout vulnerability within the AmdCpmDisplayFeatureSMM driver could allow locally…
SMM Callout vulnerability within the AmdCpmDisplayFeatureSMM driver could allow locally authenticated attackers to overwrite SMRAM, potentially resulting in arbitrary code execution.
- 7.3 High severity
Insufficient checking of memory buffer in AMD Secure Processor (ASP) Secure OS may allow an…
Insufficient checking of memory buffer in AMD Secure Processor (ASP) Secure OS may allow an attacker with a malicious trusted application to read/write to the ASP Secure OS kernel virtual address space, potentially resulting in privilege escalation.
- 7.5 High severity
3rd Gen AMD EPYC™ Processors: Improper Control of Generation of Code
Improper validation in a model specific register (MSR) could allow a malicious program with ring0 access to modify SMM configuration while SMI lock is enabled, potentially leading to arbitrary code execution.
- 8.2 High severity
AMD Ryzen™ Threadripper™ PRO Processors 5900…: Improper Access Control
A potential weakness in AMD SPI protection features may allow a malicious attacker with Ring0 (kernel mode) access to bypass the native System Management Mode (SMM) ROM protections.