Amd Epyc 9474F vulnerabilities
16 vulnerabilities
Known vulnerabilities in Amd Epyc 9474F, newest first, with CVSS severity, EPSS, KEV listings, ransomware use and the affected versions.
CVE-2021-26345amd2nd gen amd epyc™ processors+94
EPSS score0.43%
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.CVE-2021-46766amd4th gen amd epyc™ processors+30EPSS score0.23%
Improper clearing of sensitive data in the ASP Bootloader may expose secret keys to a privileged attacker accessing ASP SRAM, potentially leading to a loss of confidentiality.CVE-2021-46774amd1st gen amd epyc™ processors+149EPSS score0.51%
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.CVE-2022-23830amd3rd gen amd epyc™ processors+67EPSS score0.35%
SMM configuration may not be immutable, as intended, when SNP is enabled resulting in a potential limited loss of guest memory integrity.CVE-2024-21978amd3rd gen amd epyc™ processors+89EPSS score0.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.CVE-2024-21980amd3rd gen amd epyc™ processors+89EPSS score0.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.CVE-2023-20584amdepyc_7203_firmware+66EPSS score0.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.CVE-2023-20566amd3rd gen amd epyc™ processors+68EPSS score0.37%
Improper address validation in ASP with SNP enabled may potentially allow an attacker to compromise guest memory integrity.CVE-2023-20578amdepyc_7001_firmware+104EPSS score0.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.CVE-2023-20591amdepyc_7203_firmware+64EPSS score0.30%
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.CVE-2023-20569amd1st gen amd epyc™ processors+338EPSS score7.30%
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.CVE-2023-20573amd3rd gen amd epyc™ processors+66EPSS score0.29%
A privileged attacker
can prevent delivery of debug exceptions to SEV-SNP guests potentially
resulting in guests not receiving expected debug information.CVE-2023-20575amd1st gen amd epyc™ processors+91EPSS score0.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.CVE-2023-31347amd3rd gen amd epyc™ processors+64EPSS score0.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.CVE-2023-31346amd3rd gen amd epyc™ processors+87EPSS score0.31%
Failure to initialize
memory in SEV Firmware may allow a privileged attacker to access stale data
from other guests.CVE-2023-31355amd3rd gen amd epyc™ processors+89EPSS score0.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.