AMD AMD Radeon™ PRO V620
18 vulnérabilités publiées citent ce produit.
Tel que les CNA l’écrivent dans leurs fiches CVE (éditeur et produit) ; les versions sont les leurs.
| CVE | Versions vulnérables | Titre | Sévérité | Publiée | EPSS | Exploitation |
|---|---|---|---|---|---|---|
| CVE-2021-46747 | | Insufficient granularity of access control in ASP (AMD Secure Processor) may allow an attacker with an untrusted user space application to m | HIGH 7.1 | 0.1 % | ||
| CVE-2025-52532 | | A race condition in the MxGPU-Virtualization driver’s ioctl path caused by concurrent unsynchronized access to the global variable amdgv_cmd | LOW 2.0 | 0.1 % | ||
| CVE-2023-31309 | | Improper validation in Power Management Firmware (PMFW) may allow an attacker with privileges to pass malformed workload arguments when expo | MEDIUM 6.8 | 0.1 % | ||
| CVE-2025-54511 | | Improper handling of insufficient privileges in the AMD Secure Processor (ASP) could allow an attacker to provide an input value to a functi | MEDIUM 5.3 | 0.2 % | ||
| CVE-2025-54517 | | Out of bounds write in AMD AMDGV_CMD_GET_DIAG_DATA ioctl handler could allow a local user to escalate privileges via remote code execution. | HIGH 8.5 | 0.1 % | ||
| CVE-2025-66660 | | Insufficient parameter sanitization in TEE SOC Driver could allow an attacker to issue a malformed DRV_SOC_CMD_ID_SRIOV_CHECK_TA_COMPAT to c | LOW 1.8 | 0.1 % | ||
| CVE-2025-66664 | | Insufficient parameter sanitization in AMD Secure Processor (ASP) TEE SOC Driver could allow an attacker to issue a malformed DRV_SOC_CMD_ID | MEDIUM 4.6 | 0.1 % | ||
| CVE-2023-31316 | | Improperly preserved integrity of hardware configuration state during a power save/restore operation in the AMD Secure Processor (ASP) could | HIGH 7.1 | 0.1 % | ||
| CVE-2022-23826 | | A TOCTOU (Time-Of-Check to Time-Of-Use) in the graphics interface may allow an attacker to load registers repeatedly creating a race conditi | LOW 1.8 | 0.1 % | ||
| CVE-2021-26380 | | A compromised Trusted OS (TOS) driver could issue a malformed call that could potentially allow memory access outside the intended range re | LOW 1.8 | 0.1 % | ||
| CVE-2023-20514 | | Improper handling of parameters in the AMD Secure Processor (ASP) could allow a privileged attacker to pass an arbitrary memory value to fun | HIGH 8.7 | 0.2 % | ||
| CVE-2024-36324 | | Improper input validation in AMD Graphics Driver could allow an attacker to supply a specially crafted pointer, potentially leading to arbit | HIGH 8.8 | 0.2 % | ||
| CVE-2024-36316 | | The integer overflow vulnerability within AMD Graphics driver could allow an attacker to bypass size checks potentially resulting in a denia | MEDIUM 5.5 | 0.2 % | ||
| CVE-2021-26410 | | Improper syscall input validation in ASP (AMD Secure Processor) may force the kernel into reading syscall parameter values from its own memo | LOW 1.8 | 0.2 % | ||
| CVE-2021-26381 | | Improper system call parameter validation in the Trusted OS may allow a malicious driver to perform mapping or unmapping operations on a lar | HIGH 7.1 | 0.2 % | ||
| CVE-2024-36353 | | Insufficient clearing of GPU global memory could allow a malicious process running on the same GPU to read left over memory values potential | MEDIUM 6.5 | 0.2 % | ||
| CVE-2024-21971 | | Improper input validation in AMD Crash Defender could allow an attacker to provide the Windows® system process ID to a kernel-mode driver, r | MEDIUM 5.5 | 0.1 % | ||
| CVE-2023-20508 | | Improper access control in the ASP could allow a privileged attacker to perform an out-of-bounds write to a memory location not controlled b | MEDIUM 5.0 | 0.1 % |