Amd Ryzen™ Z2 Series Processors Extreme
6 CVEs tracked. None of them is in CISA KEV.
This hub aggregates every CVE we track for Amd Ryzen™ Z2 Series Processors Extreme, a product in the hardware firmware space. Use it to gauge the current risk picture and drill into individual advisories.
Amd Ryzen™ Z2 Series Processors Extreme CVEs per month
| Month | CVEs |
|---|---|
| 2024-10 | 0 |
| 2024-11 | 0 |
| 2024-12 | 0 |
| 2025-01 | 0 |
| 2025-02 | 0 |
| 2025-03 | 1 |
| 2025-04 | 0 |
| 2025-05 | 0 |
| 2025-06 | 0 |
| 2025-07 | 0 |
| 2025-08 | 0 |
| 2025-09 | 0 |
| 2025-10 | 0 |
| 2025-11 | 0 |
| 2025-12 | 0 |
| 2026-01 | 0 |
| 2026-02 | 1 |
| 2026-03 | 0 |
| 2026-04 | 1 |
| 2026-05 | 3 |
| 2026-06 | 0 |
| 2026-07 | 0 |
| 2026-08 | 0 |
| 2026-09 | 0 |
Severity
How the 6 CVEs score on CVSS. Severity is not exploitation: KEV is counted above.
- High1
- Medium1
- Low1
Latest CVEs
The 6 most recently published vulnerabilities affecting Amd Ryzen™ Z2 Series Processors Extreme.
- CVE-2025-48516Insecure default configuration state of DDR5 memory module by AGESA Bootloader Firmware could allow an attacker with local user privilege to abuse the unprotected PMIC interface to create a permane...—
- CVE-2025-0045Improper Input validation in the AMD Secure Processor (ASP) PCI driver may allow a local attacker to create a buffer overflow condition, potentially resulting in a crash or denial of service—
- CVE-2026-0438A System Management Mode (SMM) handler could perform a callout to code located in non-SMM/untrusted memory. A highly privileged attacker could, with active user interaction and under high complexit...—
- CVE-2025-54502Incorrect 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 resul...7.5
- CVE-2025-54514Improper isolation of shared resources on a system on a chip by a malicious local attacker with high privileges could potentially lead to a partial loss of integrity.3.3
- CVE-2024-36353Insufficient clearing of GPU global memory could allow a malicious process running on the same GPU to read left over memory values potentially leading to loss of confidentiality.6.5
Product grouping is registry-driven, with AI assist and human review. How it works