AMD Ryzen™ Embedded 8000 Series Processors vulnerabilities
13 known vulnerabilities in AMD Ryzen™ Embedded 8000 Series 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.1 High severity
AMD Ryzen™ 7035 Series Processors with Radeon™…: Unchecked Return Value
An unchecked return value within the AMD Platform Management Framework (PMF) could allow an attacker to write to an arbitrary memory address resulting in denial of service or arbitrary code execution.
- 8.4 High severity
Improper input validation within the AMD Platform Management Framework (PMF) could allow an…
Improper input validation within the AMD Platform Management Framework (PMF) could allow an attacker to unmap arbitrary memory pages potentially impacting integrity and availability, or allowing privilege escalation resulting in loss of confidentiality.
- 8.3 High severity
AMD Ryzen™ 7035 Series Processors with Radeon™…: Unchecked Return Value
An unchecked return value within the AMD Platform Management Framework (PMF) could allow an attacker to read or modify an arbitrary address potentially resulting in loss of confidentiality, integrity, or availability.
- 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.
- 8.5 High severity
AMD Ryzen™ 7035 Series Processors with Radeon™…: Out-of-bounds Write
An improper input validation vulnerability within the AMD Platform Management Framework (PMF) Driver can allow a local attacker to write Out-of-Bounds, potentially resulting in privilege escalation.
- 8.5 High severity
AMD Ryzen™ 7035 Series Processors with Radeon™…: Out-of-bounds Write
An improper input validation vulnerability within the AMD Platform Management Framework (PMF) driver can allow a local attacker to read or write Out-of-Bounds, potentially resulting in privilege escalation
- 7.0 High severity
AMD Ryzen™ 4000 Series Mobile Processors with…: Incorrect Default Permissions
Incorrect default permissions in the installation directory for the AMD general-purpose input/output controller (GPIO) 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.3 High severity
AMD EPYC™ 7001 Series Processors: Improper Restriction of Operations within the Bounds of a Memory Buffer
Improper 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 machine check error resulting in denial of service.
- 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.
- 8.8 High severity
AMD Ryzen™ 6000 Series Processors with Radeon™…: Out-of-bounds Write
Improper input validation in AMD Graphics Driver could allow an attacker to supply a specially crafted pointer, potentially leading to arbitrary code execution.
- 7.0 High severity
AMD Ryzen™ 4000 Series Mobile Processors with…: Integer Overflow or Wraparound
Integer 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
- 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.