AMD Epyc 4005 Series Processors vulnerabilities

6 CVEs affecting AMD Epyc 4005 Series Processors, 0 known to be exploited (CISA KEV), with EPSS scores. Latest: CVE-2024-21962, published 2026-05-15.

More from AMD.

Highest priority

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

• CVE-2026-0438, published 2026-05-15. Medium severity, CVSS 5.4. EPSS: 0.1% chance of exploitation in the next 30 days. A 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 complexity…
• CVE-2025-0045, published 2026-05-15. Medium severity, CVSS 6.9. EPSS: 0.1% chance of exploitation in the next 30 days. Improper 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-2024-21962, published 2026-05-15. High severity, CVSS 8.6. EPSS: 0.1% chance of exploitation in the next 30 days. Improper Input Validation in the AMD RAID driver could allow an attacker to point to an arbitrary memory location potentially resulting in privilege escalation and arbitrary code execution.
• CVE-2025-48512, published 2026-05-15. High severity, CVSS 7.0. EPSS: 0.1% chance of exploitation in the next 30 days. Incorrect default permissions in the installation directory for the AMD general-purpose input/output controller (GPIO) could allow an attacker to achieve privilege escalation resulting in arbitrary…
• CVE-2026-0432, published 2026-05-15. High severity, CVSS 8.5. EPSS: 0.1% chance of exploitation in the next 30 days. Incorrect default permissions in the installation directory for the AMD chipset driver could allow an attacker to achieve privilege escalation resulting in arbitrary code execution.
• CVE-2025-48521, published 2026-05-15. Medium severity, CVSS 6.9. EPSS: 0.1% chance of exploitation in the next 30 days. Improper input validation in the AMD Secure Processor (ASP) PCI driver could allow a local attacker to trigger a Use-After-Free (UAF) condition, potentially resulting in a loss of platform integrity…