Epyc 73f3 Firmware vulnerabilities
7 known vulnerabilities in Epyc 73f3 Firmware from AMD. 7 are rated high or critical. Each entry lists the affected versions and the release that fixes it, where the vendor has published one.
Latest first
- 10.0 Critical severity
AMD EPYC™ 7003 Series Processors: Improper Initialization
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.
- 7.9 High severity
3rd Gen AMD EPYC™ Processors: Out-of-bounds Write
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.
- 7.9 High severity
Improper input validation in SEV-SNP could allow a malicious hypervisor to read or overwrite…
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.
- 7.5 High severity
2nd Gen AMD EPYC™: Out-of-bounds Write
An attacker with a compromised ASP could possibly send malformed commands to an ASP on another CPU, resulting in an out of bounds write, potentially leading to a loss a loss of integrity.
- 9.8 Critical severity
1st Gen AMD EPYC™: Out-of-bounds Write
Improper access control settings in ASP Bootloader may allow an attacker to corrupt the return address causing a stack-based buffer overrun potentially leading to arbitrary code execution.
- 7.5 High severity
2nd Gen EPYC: Improper Restriction of Operations within the Bounds of a Memory Buffer
Insufficient bound checks in the SMU may allow an attacker to update the SRAM from/to address space to an invalid value potentially resulting in a denial of service.
- 7.5 High severity
2nd Gen EPYC: Improper Restriction of Operations within the Bounds of a Memory Buffer
Insufficient bound checks in the SMU may allow an attacker to update the from/to address space to an invalid value potentially resulting in a denial of service.