Improper input validation in the SMM handler may allow a privileged attacker to overwrite SMRAM, potentially leading to arbitrary code execution.
Product
AMD EPYC™ 7003 Processors vulnerabilities
8 published CVES affecting AMD EPYC™ 7003 Processors, from public sources (CVE.org, NVD, CISA KEV, FIRST EPSS, OSV).
- Total
- 8
- Critical
- 0
- High
- 4
- Medium
- 4
- Low
- 0
- Unscored
- 0
- CISA KEV
- 0
Latest AMD EPYC™ 7003 Processors CVEs
Newest publication first
-
HighCVSS 7.5 EPSS 0.18%
-
HighCVSS 7.5 EPSS 0.18%
Improper input validation in the SMM handler may allow a privileged attacker to overwrite SMRAM, potentially leading to arbitrary code execution.
-
HighCVSS 7.5 EPSS 0.18%
Improper input validation in the SMM handler may allow a privileged attacker to overwrite SMRAM, potentially leading to arbitrary code execution.
-
HighCVSS 8.2 EPSS 0.20%
Improper input validation within the AmdPspP2CmboxV2 driver may allow a privileged attacker to overwrite SMRAM, leading to arbitrary code execution.
-
MediumCVSS 4.4 EPSS 0.21%
Incomplete system memory cleanup in SEV firmware could allow a privileged attacker to corrupt guest private memory, potentially resulting in a loss of data integrity.
-
MediumCVSS 6.0 EPSS 0.19%
IOMMU improperly handles certain special address ranges with invalid device table entries (DTEs), which may allow an attacker with privileges and a compromised Hypervisor to induce DTE faults to bypass RMP checks in SEV-SNP, potentially leading to a loss of guest integrity.
-
MediumCVSS 6.4 EPSS 0.12%
A TOCTOU (Time-Of-Check-Time-Of-Use) in SMM may allow an attacker with ring0 privileges and access to the BIOS menu or UEFI shell to modify the communications buffer potentially resulting in arbitrary code execution.
-
MediumCVSS 5.2 EPSS 0.15%
Lack of stack protection exploit mechanisms in ASP Secure OS Trusted Execution Environment (TEE) may allow a privileged attacker with access to AMD signing keys to c006Frrupt the return address, causing a stack-based buffer overrun, potentially leading to a denial of service.
Sources: CVE.org, NVD, CISA KEV, FIRST EPSS, OSV and public exploit-reference metadata. Product matching comes from the published CVE records. A proof-of-concept means public code exists; it is not evidence of exploitation.