AMD Ryzen™ 4000 Series Desktop Processors With Radeon™ Graphics vulnerabilities
6 vulnerabilities
Known vulnerabilities in AMD Ryzen™ 4000 Series Desktop Processors With Radeon™ Graphics, newest first, with CVSS severity, EPSS, KEV listings, ransomware use and the affected versions.
CVE-2021-26344amdamd athlon™ 3000 series desktop processors with radeon™ graphics+83
EPSS score0.16%
An out of bounds memory write when processing the AMD
PSP1 Configuration Block (APCB) could allow an attacker with access the ability
to modify the BIOS image, and the ability to sign the resulting image, to
potentially modify the APCB block resulting in arbitrary code execution.CVE-2021-46772amdamd athlon™ 3000 series desktop processors with radeon™ graphics+13EPSS score0.18%
Insufficient input validation in the ABL may allow a privileged
attacker with access to the BIOS menu or UEFI shell to tamper with the
structure headers in SPI ROM causing an out of bounds memory read and write,
potentially resulting in memory corruption or denial of service.CVE-2022-23829amd1st gen amd epyc™ processors+23EPSS score0.20%
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.CVE-2024-21981amdamd athlon™ 3000 series desktop processors with radeon™ graphics+19EPSS score0.14%
Improper key usage control in AMD Secure Processor
(ASP) may allow an attacker with local access who has gained arbitrary code
execution privilege in ASP to
extract ASP cryptographic keys, potentially resulting in loss of
confidentiality and integrity.CVE-2023-20579amdamd ryzen™ 3000 series processors with radeon™ graphics+142EPSS score0.16%
Improper
Access Control in the AMD SPI protection feature may allow a user with Ring0
(kernel mode) privileged access to bypass protections potentially resulting in
loss of integrity and availability.CVE-2023-31315amd1st gen amd epyc™ processors+74EPSS score0.63%
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.