AMD Ryzen Pro Firmware vulnerabilities
7 CVEs affecting AMD Ryzen Pro Firmware, 0 known to be exploited (CISA KEV), with EPSS scores. Latest: CVE-2021-26318, published 2021-10-13.
More from AMD.
Highest priority
Known exploited (CISA KEV) first, then by EPSS exploit probability.
- CVE-2018-8936, published 2018-03-22. Critical severity, CVSS 9.0. EPSS: 1.8% chance of exploitation in the next 30 days. The AMD EPYC Server, Ryzen, Ryzen Pro, and Ryzen Mobile processor chips allow Platform Security Processor (PSP) privilege escalation.
- CVE-2018-8935, published 2018-03-22. Critical severity, CVSS 9.0. EPSS: 1.8% chance of exploitation in the next 30 days. The Promontory chipset, as used in AMD Ryzen and Ryzen Pro platforms, has a backdoor in the ASIC, aka CHIMERA-HW.
- CVE-2018-8934, published 2018-03-22. Critical severity, CVSS 9.0. EPSS: 1.8% chance of exploitation in the next 30 days. The Promontory chipset, as used in AMD Ryzen and Ryzen Pro platforms, has a backdoor in firmware, aka CHIMERA-FW.
- CVE-2018-8930, published 2018-03-22. Critical severity, CVSS 9.0. EPSS: 1.8% chance of exploitation in the next 30 days. The AMD EPYC Server, Ryzen, Ryzen Pro, and Ryzen Mobile processor chips have insufficient enforcement of Hardware Validated Boot, aka MASTERKEY-1, MASTERKEY-2, and MASTERKEY-3.
- CVE-2018-8932, published 2018-03-22. Critical severity, CVSS 9.0. EPSS: 1.7% chance of exploitation in the next 30 days. The AMD Ryzen and Ryzen Pro processor chips have insufficient access control for the Secure Processor, aka RYZENFALL-2, RYZENFALL-3, and RYZENFALL-4.
- CVE-2018-8931, published 2018-03-22. Critical severity, CVSS 9.0. EPSS: 1.7% chance of exploitation in the next 30 days. The AMD Ryzen, Ryzen Pro, and Ryzen Mobile processor chips have insufficient access control for the Secure Processor, aka RYZENFALL-1.
- CVE-2021-26318, published 2021-10-13. Medium severity, CVSS 4.7. EPSS: 0.3% chance of exploitation in the next 30 days. A timing and power-based side channel attack leveraging the x86 PREFETCH instructions on some AMD CPUs could potentially result in leaked kernel address space information.