AMD Ryzen 5 2600x Firmware vulnerabilities

24 CVEs affecting AMD Ryzen 5 2600x Firmware, 0 known to be exploited (CISA KEV), with EPSS scores. Latest: CVE-2021-26354, published 2023-05-09.

More from AMD.

Highest priority

Known exploited (CISA KEV) first, then by EPSS exploit probability.

• CVE-2022-29900, published 2022-07-12. Medium severity, CVSS 6.5. EPSS: 3.9% chance of exploitation in the next 30 days. Mis-trained branch predictions for return instructions may allow arbitrary speculative code execution under certain microarchitecture-dependent conditions.
• CVE-2022-23823, published 2022-06-15. Medium severity, CVSS 6.5. EPSS: 1.2% chance of exploitation in the next 30 days. A potential vulnerability in some AMD processors using frequency scaling may allow an authenticated attacker to execute a timing attack to potentially enable information disclosure.
• CVE-2022-23825, published 2022-07-14. Medium severity, CVSS 6.5. EPSS: 0.8% chance of exploitation in the next 30 days. Aliases in the branch predictor may cause some AMD processors to predict the wrong branch type potentially leading to information disclosure.
• CVE-2023-20559, published 2023-04-02. High severity, CVSS 8.8. EPSS: 0.7% chance of exploitation in the next 30 days. Insufficient control flow management in AmdCpmGpioInitSmm may allow a privileged attacker to tamper with the SMM handler potentially leading to escalation of privileges.
• CVE-2023-20558, published 2023-04-02. High severity, CVSS 8.8. EPSS: 0.7% chance of exploitation in the next 30 days. Insufficient control flow management in AmdCpmOemSmm may allow a privileged attacker to tamper with the SMM handler potentially leading to an escalation of privileges.
• CVE-2022-23824, published 2022-11-09. Medium severity, CVSS 5.5. EPSS: 0.6% chance of exploitation in the next 30 days. IBPB may not prevent return branch predictions from being specified by pre-IBPB branch targets leading to a potential information disclosure.
• CVE-2021-26341, published 2022-03-11. Medium severity, CVSS 6.5. EPSS: 0.3% chance of exploitation in the next 30 days. Some AMD CPUs may transiently execute beyond unconditional direct branches, which may potentially result in data leakage.
• CVE-2021-26401, published 2022-03-11. Medium severity, CVSS 5.6. EPSS: 0.3% chance of exploitation in the next 30 days. LFENCE/JMP (mitigation V2-2) may not sufficiently mitigate CVE-2017-5715 on some AMD CPUs.
• CVE-2021-26317, published 2022-05-12. High severity, CVSS 7.8. EPSS: 0.3% chance of exploitation in the next 30 days. Failure to verify the protocol in SMM may allow an attacker to control the protocol and modify SPI flash resulting in a potential arbitrary code execution.
• CVE-2022-27672, published 2023-03-01. Medium severity, CVSS 4.7. EPSS: 0.3% chance of exploitation in the next 30 days. When SMT is enabled, certain AMD processors may speculatively execute instructions using a target from the sibling thread after an SMT mode switch potentially resulting in information disclosure.

Latest

• CVE-2021-26354, published 2023-05-09. Medium severity, CVSS 5.5. EPSS: 0.2% chance of exploitation in the next 30 days. Insufficient bounds checking in ASP may allow an attacker to issue a system call from a compromised ABL which may cause arbitrary memory values to be initialized to zero, potentially leading to…
• CVE-2021-26316, published 2023-01-11. High severity, CVSS 7.8. EPSS: 0.3% chance of exploitation in the next 30 days. Failure to validate the communication buffer and communication service in the BIOS may allow an attacker to tamper with the buffer resulting in potential SMM (System Management Mode) arbitrary code…
• CVE-2021-46778, published 2022-08-10. Medium severity, CVSS 5.6. EPSS: 0.2% chance of exploitation in the next 30 days. Execution unit scheduler contention may lead to a side channel vulnerability found on AMD CPU microarchitectures codenamed “Zen 1”, “Zen 2” and “Zen 3” that use simultaneous multithreading (SMT). By…
• CVE-2021-26384, published 2022-07-14. High severity, CVSS 7.8. EPSS: 0.2% chance of exploitation in the next 30 days. A malformed SMI (System Management Interface) command may allow an attacker to establish a corrupted SMI Trigger Info data structure, potentially leading to out-of-bounds memory reads and writes when…