AMD Ryzen™ Threadripper™ 3000 Series Processors vulnerabilities
6 vulnerabilities
Known vulnerabilities in AMD Ryzen™ Threadripper™ 3000 Series Processors, 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-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-2024-36349amdamd athlon™ 3000 series desktop processors with radeon™ graphics+39EPSS score0.19%
A 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.CVE-2024-36348amdamd athlon™ 3000 series desktop processors with radeon™ graphics+33EPSS score0.34%
A 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 information leakage.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.