Improper re-initialization of IOMMU during the DRTM event may permit an untrusted platform configuration to persist, allowing an attacker to read or modify hypervisor memory, potentially resulting in loss of confidentiality, integrity, and availability.
Product
amd epyc 7643 firmware vulnerabilities
96 published CVES affecting amd epyc 7643 firmware, from public sources (CVE.org, NVD, CISA KEV, FIRST EPSS, OSV).
- Total
- 96
- Critical
- 5
- High
- 37
- Medium
- 51
- Low
- 3
- Unscored
- 0
- CISA KEV
- 0
Latest amd epyc 7643 firmware CVEs
Newest publication first · page 1 of 4
-
CriticalCVSS 10.0 EPSS 0.30%
-
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.
-
HighCVSS 8.2 EPSS 0.16%
An out of bounds memory write when processing the AMD PSP1 Configuration Block (APCB) could allow an attacker with access the ability to modify the BIOS image, and the ability to sign the resulting image, to potentially modify the APCB block resulting in 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.
-
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.
-
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.
-
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.
-
HighCVSS 7.4 EPSS 0.40%
A TOCTOU in ASP bootloader may allow an attacker to tamper with the SPI ROM following data read to memory potentially resulting in S3 data corruption and information disclosure.
-
MediumCVSS 5.5 EPSS 0.18%
Insufficient bounds checking in ASP may allow an attacker to issue a system call from a compromised ABL which may cause arbitrary memory values to be initialized to zero, potentially leading to a loss of integrity.
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.