Advanced Micro Devices (AMD) Ryzen 5 6600h Firmware Rembrandtpi-fp7 1.0.0.8

CPE Details

Advanced Micro Devices (AMD) Ryzen 5 6600h Firmware Rembrandtpi-fp7 1.0.0.8
rembrandtpi-fp7_1.0.0.8
2023-08-21
10h43 +00:00
2023-08-21
16h35 +00:00
Alerte pour un CPE
Stay informed of any changes for a specific CPE.
Notifications manage

CPE Name: cpe:2.3:o:amd:ryzen_5_6600h_firmware:rembrandtpi-fp7_1.0.0.8:*:*:*:*:*:*:*

Informations

Vendor

amd

Product

ryzen_5_6600h_firmware

Version

rembrandtpi-fp7_1.0.0.8

Related CVE

Open and find in CVE List

CVE ID Published Description Score Severity
CVE-2023-20579 2024-02-13 19h32 +00:00 Improper Access Control in the AMD SPI protection feature may allow a user with Ring0 (kernel mode) privileged access to bypass protections potentially resulting in loss of integrity and availability.
6
Medium
CVE-2023-20596 2023-11-14 18h55 +00:00 Improper input validation in the SMM Supervisor may allow an attacker with a compromised SMI handler to gain Ring0 access potentially leading to arbitrary code execution.
9.8
Critical
CVE-2023-20571 2023-11-14 18h55 +00:00 A race condition in System Management Mode (SMM) code may allow an attacker using a compromised user space to leverage CVE-2018-8897 potentially resulting in privilege escalation.
8.1
High
CVE-2023-20565 2023-11-14 18h54 +00:00 Insufficient protections in System Management Mode (SMM) code may allow an attacker to potentially enable escalation of privilege via local access.
7.8
High
CVE-2023-20563 2023-11-14 18h54 +00:00 Insufficient protections in System Management Mode (SMM) code may allow an attacker to potentially enable escalation of privilege via local access.
7.8
High
CVE-2023-20569 2023-08-08 17h02 +00:00 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.
4.7
Medium
CVE-2021-26365 2023-05-09 18h58 +00:00 Certain size values in firmware binary headers could trigger out of bounds reads during signature validation, leading to denial of service or potentially limited leakage of information about out-of-bounds memory contents.
8.2
High