A heap overflow in SMM module may allow an attacker with access to a second vulnerability that enables writing to SPI flash, potentially resulting in arbitrary code execution.
Product
amd 3rd Gen AMD EPYC™ Processors vulnerabilities
27 published CVES affecting amd 3rd Gen AMD EPYC™ Processors, from public sources (CVE.org, NVD, CISA KEV, FIRST EPSS, OSV).
- Total
- 27
- Critical
- 2
- High
- 10
- Medium
- 13
- Low
- 2
- Unscored
- 0
- CISA KEV
- 0
Latest amd 3rd Gen AMD EPYC™ Processors CVEs
Newest publication first · page 1 of 2
-
HighCVSS 7.4 EPSS 0.15%
-
HighCVSS 7.5 EPSS 0.63%
Improper validation in a model specific register (MSR) could allow a malicious program with ring0 access to modify SMM configuration while SMI lock is enabled, potentially leading to arbitrary code execution.
-
HighCVSS 7.9 EPSS 0.45%
Improper restriction of write operations in SNP firmware could allow a malicious hypervisor to potentially overwrite a guest's memory or UMC seed resulting in loss of confidentiality and integrity.
-
HighCVSS 7.9 EPSS 0.49%
Improper input validation in SEV-SNP could allow a malicious hypervisor to read or overwrite guest memory potentially leading to data leakage or data corruption.
-
MediumCVSS 6.0 EPSS 0.44%
Improper restriction of write operations in SNP firmware could allow a malicious hypervisor to overwrite a guest's UMC seed potentially allowing reading of memory from a decommissioned guest.
-
HighCVSS 8.2 EPSS 0.20%
A potential weakness in AMD SPI protection features may allow a malicious attacker with Ring0 (kernel mode) access to bypass the native System Management Mode (SMM) ROM protections.
-
HighCVSS 7.1 EPSS 0.17%
Improper Access Control in System Management Mode (SMM) may allow an attacker access to the SPI flash potentially leading to arbitrary code execution.
-
MediumCVSS 4.9 EPSS 0.46%
Due to a code bug in Secure_TSC, SEV firmware may allow an attacker with high privileges to cause a guest to observe an incorrect TSC when Secure TSC is enabled potentially resulting in a loss of guest integrity.
-
MediumCVSS 6.0 EPSS 0.31%
Failure to initialize memory in SEV Firmware may allow a privileged attacker to access stale data from other guests.
-
LowCVSS 3.2 EPSS 0.29%
A privileged attacker can prevent delivery of debug exceptions to SEV-SNP guests potentially resulting in guests not receiving expected debug information.
-
MediumCVSS 6.5 EPSS 1.2%
Improper or unexpected behavior of the INVD instruction in some AMD CPUs may allow an attacker with a malicious hypervisor to affect cache line write-back behavior of the CPU leading to a potential loss of guest virtual machine (VM) memory integrity.
-
HighCVSS 7.5 EPSS 0.43%
Improper address validation in ASP with SNP enabled may potentially allow an attacker to compromise guest memory integrity.
-
LowCVSS 3.3 EPSS 0.22%
A Use-After-Free vulnerability in the management of an SNP guest context page may allow a malicious hypervisor to masquerade as the guest's migration agent resulting in a potential loss of guest integrity.
-
MediumCVSS 5.3 EPSS 0.40%
SMM configuration may not be immutable, as intended, when SNP is enabled resulting in a potential limited loss of guest memory integrity.
-
MediumCVSS 4.9 EPSS 0.51%
Failure to validate the value in APCB may allow a privileged attacker to tamper with the APCB token to force an out-of-bounds memory read potentially resulting in a denial of service.
-
HighCVSS 7.5 EPSS 0.55%
Insufficient DRAM address validation in System Management Unit (SMU) may allow an attacker to read/write from/to an invalid DRAM address, potentially resulting in denial-of-service.
-
MediumCVSS 4.6 EPSS 0.36%
Insufficient input validation in the ASP Bootloader may enable a privileged attacker with physical access to expose the contents of ASP memory potentially leading to a loss of confidentiality.
-
MediumCVSS 5.7 EPSS 0.30%
TOCTOU in the ASP Bootloader may allow an attacker with physical access to tamper with SPI ROM records after memory content verification, potentially leading to loss of confidentiality or a denial of service.
-
CriticalCVSS 9.8 EPSS 0.71%
Failure to validate the AMD SMM communication buffer may allow an attacker to corrupt the SMRAM potentially leading to arbitrary code execution.
-
HighCVSS 7.5 EPSS 0.57%
Insufficient DRAM address validation in System Management Unit (SMU) may allow an attacker to read/write from/to an invalid DRAM address, potentially resulting in denial-of-service.
-
MediumCVSS 4.4 EPSS 0.19%
Improper initialization of variables in the DXE driver may allow a privileged user to leak sensitive information via local access.
-
MediumCVSS 4.7 EPSS 7.3%
A side channel vulnerability on some of the AMD CPUs may allow an attacker to influence the return address prediction. This may result in speculative execution at an attacker-controlled address, potentially leading to information disclosure.
-
MediumCVSS 6.5 EPSS 0.80%
A potential power side-channel vulnerability in some AMD processors may allow an authenticated attacker to use the power reporting functionality to monitor a program’s execution inside an AMD SEV VM potentially resulting in a leak of sensitive information.
-
CriticalCVSS 9.1 EPSS 0.65%
Insufficient validation of inputs in SVC_MAP_USER_STACK in the ASP (AMD Secure Processor) bootloader may allow an attacker with a malicious Uapp or ABL to send malformed or invalid syscall to the bootloader resulting in a potential denial of service and loss of integrity.
-
MediumCVSS 5.5 EPSS 0.19%
A compromised or malicious ABL or UApp could send a SHA256 system call to the bootloader, which may result in exposure of ASP memory to userspace, potentially leading to information disclosure.
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.