AMD Graphics Vulnerabilities – November 2026
Summary
Vulnerabilities potentially impacting AMD Instinct™ Accelerators and AMD Radeon™ Graphics Products were reported and AMD has provided mitigations.
CVE Details
Refer to Glossary for explanation of terms
CVE |
CVE Description |
CVSS Base Score |
CVE-2024-36313 |
Improper input validation in the AMD Video Decoder Engine Firmware (VCN FW) could allow an attacker to craft a specially encoded video that, if processed by the affected firmware, could result in memory corruption and potentially impact system confidentiality, integrity, or availability. |
8.9 |
CVE-2024-36325 |
Improper isolation of privileged SoC registers from commands submitted by user-mode processes and processed by the AMD Video Decoder Engine hardware (VCN JPEG hardware) engine command processor could allow a user-mode process to potentially achieve privilege escalation and obtain read and write access to kernel memory. |
8.8 |
CVE-2025-0047 |
Improper validation of specified type of input in the AMD Video Decoder Engine Firmware (VCN FW) could allow an attacker with access to the VCN engine to corrupt firmware memory and achieve privilege escalation, potentially impacting confidentiality, integrity and availability. |
8.8 |
CVE-2024-21940 |
Insufficient granularity of access control separation in VCN HW could allow an attacker with elevated privileges to modify memory configuration settings and gain access to protected memory reserved for VCN, potentially resulting in loss of confidentiality, integrity, and availability. |
8.7 |
CVE-2026-40680 |
A use-after-free condition in the AMDGPU Linux kernel driver could allow a local unprivileged attacker to bypass CPU memory protection mechanisms, potentially resulting in loss of confidentiality, integrity, and availability. |
8.5 |
CVE-2026-0442 |
Improper validation of inputs in the AMD Radeon™ Kernel Driver could allow an attacker to perform arbitrary kernel memory writes potentially leading to privilege escalation and/or arbitrary code execution. |
8.4 |
CVE-2026-0002 |
Improper isolation of GPU SMUIO I2C controller could allow a user-privileged attacker to perform malicious I2C commands to connected I2C devices that could potentially result in a denial-of-service condition of the GPU device. |
7.0 |
CVE-2026-0443 |
Improper handling of parameters in the AMD Radeon™ Kernel Driver could allow a specially crafted executable run by an authorized user to operate with elevated privileges, potentially impacting system confidentiality, integrity, or availability. |
7.0 |
CVE-2026-0445 |
A buffer overflow in the AMD Radeon™ kernel driver could allow an attacker to overwrite kernel memory potentially leading to loss of integrity or availability. |
7.0 |
CVE-2026-0446 |
Improper handling of parameters in the AMD Radeon™ kernel driver could allow an attacker to write to an arbitrary kernel address potentially resulting in privilege escalation resulting in loss of confidentiality, integrity, and availability. |
7 |
CVE-2024-36344 |
Insufficient parameter sanitization in AMD Secure Processor (ASP) TEE DrvSys could allow an attacker with local access to the Trusted Execution Environment (TEE) interface or Trusted Application (TA) to cause an out-of-bounds write, potentially resulting in a loss of platform integrity or denial of service. |
6.9 |
CVE-2026-0425 |
Improper input validation in the AMD GPU Driver can allow a local attacker to trigger a use-after-free condition, potentially resulting in memory corruption or denial of service. |
6.9 |
CVE-2024-36322 |
Improper isolation of the AMD Video Decoder Engine hardware (VCN HW) Reliability, Availability, and Serviceability (RAS) error control register could allow a malicious guest virtual machine (VM) to trigger a fatal error condition by performing unauthorized write to that register and create a denial of service (DoS) condition affecting the host system or other guest VMs. |
6.8 |
CVE-2026-0423 |
Improper input validation in the AMD GPU driver could allow a local attacker to trigger unbounded memory allocations, potentially resulting in a denial of service. |
6.8 |
CVE-2026-0453 |
Improper input validation in the AMD Video Decoder Engine hardware (VCN JPEG hardware) could allow an attacker with local access to craft malicious input in a command buffer submitted to hardware, potentially resulting in loss of availability. |
6.8 |
CVE-2025-66661 |
A heap-based buffer overflow in the AMD Radeon™ Kernel Driver could allow an attacker to achieve privilege escalation potentially leading to arbitrary code execution. |
5.9 |
CVE-2024-36317 |
Execution with unnecessary privileges in the AMD Video Decoder Engine Firmware (VCN FW) could allow a privileged attacker to submit a maliciously crafted command causing the VCN FW to perform read/writes HW registers, potentially impacting confidentiality, integrity and/or availability. |
6.2 |
CVE-2026-0456 |
Insufficient granularity of access control in the AMD Secure Processor (ASP) Trusted Execution Environment (TEE) kernel could allow an attacker with local access to deliver malicious input via the Supervisor Call (SVC) interface, potentially resulting in information leakage, loss of platform integrity, or denial of service. |
5.8 |
CVE-2026-0464 |
A race condition in the kernel driver could create conditions that result in use-after-free condition, potentially allowing privilege escalation. |
5.8 |
CVE-2026-40673 |
A race condition in the kernel driver could result in a use-after-free condition, potentially allowing an attacker to obtain elevated privileges. |
5.8 |
CVE-2025-66663 |
Insufficient validation of DRAM addresses in AMD Secure Processor (ASP) firmware may allow an attacker with physical access to potentially bypass the Triple Modular Redundancy (TMR) protections, potentially resulting in loss of integrity and availability. |
5.7 |
CVE-2026-0422 |
A use-after-free condition in the AMD GPU driver could allow a local attacker to trigger a race condition, potentially resulting in a denial of service. |
5.7 |
CVE-2026-28236 |
Missing IOCTL input validation in the kernel driver could allow a local attacker to achieve privilege escalation, potentially resulting in arbitrary code execution. |
5.4 |
CVE-2026-0457 |
Improper isolation of the GPU HW register field could allow a user-privileged attacker to access trace data from another user process potentially leading to cross-process information leakage resulting in loss of confidentiality. |
5.3 |
CVE-2025-66662 |
Use of an out-of-range pointer offset within AMD Crash Defender could allow an attacker with local access to execute a specially crafted executable, potentially resulting in a crash or denial of service (DoS). |
5.1 |
CVE-2026-0439 |
A kernel buffer overflow in the AMD Radeon™ Kernel Driver could allow an attacker to trigger a buffer overrun in operating system-created buffers, potentially resulting in a crash resulting in loss of availability. |
5.1 |
CVE-2026-0472 |
An uncaught exception in the Windows Kernel Mode Display Driver could allow an attacker to cause a system crash resulting in denial of service. |
5.1 CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:P/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N |
CVE-2026-0444 |
A NULL pointer dereference in the AMD Radeon™ kernel driver could allow an attacker to cause system instability resulting in denial of service. |
5.1 |
CVE-2026-0447 |
A divide by zero in the AMD Radeon™ Kernel Driver could allow an attacker to trigger a system crash, potentially resulting in loss of availability. |
5.1 |
CVE-2026-0449 |
A buffer overflow in the AMD Radeon™ Kernel Driver could allow an attacker to use a malicious escape request to overwrite kernel memory or cause a system crash, potentially resulting in loss of integrity or availability. |
5.1 |
CVE-2026-0463 |
A NULL pointer deference in AMD GPU kernel driver code could allow a local attacker with limited privileges to trigger a system crash, potentially resulting in loss of availability. |
5.1 |
CVE-2026-0468 |
Improper buffer validation in the AMD Radeon™ Kernel Driver (amdfendr.sys) version 25.9.1 could allow an unprivileged user to trigger an out-of-bounds write in the \Device\AmdLog IOCTL handler, potentially resulting in a denial of service. |
5.1 |
CVE-2026-0469 |
An out-of-bounds memory access vulnerability in the AMD Radeon™ Kernel Driver (amdfendr.sys) could allow a local attacker with limited privileges to submit a specially crafted DeviceIoControl request, potentially resulting in a denial-of-service condition. |
5.1 |
CVE-2025-62622 |
Exposure of sensitive information in AMD Crash Defender could allow an attacker to cause a kernel-mode address to be written to the user-controlled output buffer, potentially resulting in a loss of confidentiality. |
4.8 |
CVE-2026-0426 |
Improper input validation in the AMD GPU driver could allow a local attacker to trigger an integer overflow condition, potentially resulting in an out-of-bounds memory access. |
4.8 |
CVE-2026-0440 |
Exposure of sensitive information to an unauthorized actor in the AMD Radeon™ driver could leak kernel addresses resulting in loss of confidentiality, or allow an attacker to allocate infinite memory causing a system crash resulting in loss of availability. |
4.8 |
CVE-2026-0448 |
Exposure of internal kernel object addresses in the AMD Crash Defender kernel driver could allow a local user to infer aspects of kernel memory layout, potentially resulting in information disclosure. |
4.8 |
CVE-2026-0451 |
Exposure of internal kernel object addresses in the AMD Defender kernel driver could allow a local user to infer aspects of kernel memory layout, potentially resulting in information disclosure. |
4.8 |
CVE-2026-0452 |
Exposure of internal kernel object addresses in the AMD Defender kernel driver could allow a local user to infer aspects of kernel memory layout, potentially resulting in information disclosure. |
4.8 |
CVE-2026-0471 |
Insertion of sensitive information into sent data in the AMD Crash Defender kernel driver could allow a local attacker to obtain information about internal kernel object addresses, potentially facilitating inference of kernel memory layout and impacting address randomization protections. |
4.8 |
CVE-2026-0477 |
Improper removal of sensitive information before storage or transfer in AMD Crash Defender could allow an attacker to obtain kernel address information potentially resulting in loss of confidentiality. |
4.8 |
CVE-2026-0478 |
Improper removal of sensitive information before storage or transfer in AMD Crash Defender could allow an attacker to obtain kernel address information potentially resulting in loss of confidentiality. |
4.8 |
CVE-2026-0479 |
Improper removal of sensitive information before storage or transfer in AMD Crash Defender could allow an attacker to obtain kernel address information potentially resulting in loss of confidentiality. |
4.8 |
CVE-2026-0459 |
A use-after-free condition in the AMD Radeon™ Open Compute System Management Interface (ROCm-SMI) could allow an attacker to access a stale pointer potentially resulting in loss of availability or confidentiality. |
2.1 |
Specific CVSS scores may change subject to your implementation. We encourage you to calculate CVSS scores independently for your system.
Affected Products and Mitigation
AMD recommends implementing the mitigated version indicated below.
*Note: Products believed to not be affected by the listed CVEs are not included.
AMD Radeon™ Series Graphics Products
Product |
CVE ID |
Mitigation |
Mitigation Release Date |
AMD Radeon™ AI PRO R9000 Series Graphics Products |
CVE-2026-0453 |
Radeon™ Software for Linux 26.14 |
2026-08-26 |
CVE-2024-36313 |
|||
CVE-2025-0047 |
|||
CVE-2026-40680 |
Radeon™ Software for Linux 26.13 |
2026-07-20 |
|
CVE-2026-0439 |
AMD Software: Adrenalin Edition 26.6.1 |
2026-06-02 |
|
CVE-2026-0445 |
|||
CVE-2026-0449 |
|||
CVE-2026-0469 |
|||
CVE-2024-21940 |
Radeon Software for Linux 26.12 |
2026-05-20 |
|
CVE-2026-0002 |
|||
CVE-2026-0422 |
|||
CVE-2026-0423 |
|||
CVE-2026-0425 |
|||
CVE-2026-0463 |
|||
CVE-2026-0464 |
|||
CVE-2026-28236 |
|||
CVE-2026-40673 |
|||
CVE-2026-0443 |
AMD Software: Adrenalin Edition 26.5.2 |
2026-05-14 |
|
CVE-2026-0446 |
|||
CVE-2026-0478 |
AMD Software: Adrenalin Edition 26.3.1 |
2026-03-19 |
|
CVE-2026-0002 |
AMD Software: Adrenalin Edition 26.3.1 |
2026-03-19 |
|
CVE-2026-0440 |
|||
CVE-2026-0442 |
|||
CVE-2026-0444 |
|||
CVE-2026-0447 |
|||
CVE-2026-0472 |
|||
CVE-2026-0477 |
AMD Software: Adrenalin Edition 26.3.1 |
2026-03-19 |
|
CVE-2026-0479 |
|||
CVE-2026-0471 |
Adrenalin Edition 26.3.1 |
2026-03-19 |
|
CVE-2024-21940 |
AMD Software: Adrenalin Edition 26.1.1 |
2026-01-21 |
|
CVE-2026-0448 |
|||
CVE-2026-0452 |
|||
CVE-2026-0468 |
|||
CVE-2025-62622 |
AMD Software: Adrenalin Edition 25.12.1 (25.20.29.09) |
2025-12-10 |
|
CVE-2025-66662 |
|||
CVE-2026-0451 |
|||
CVE-2026-0459 |
ROCm 7.1 |
2025-10-30 |
|
CVE-2024-36317 |
AMD Software: PRO Edition 25.Q3.1 (25.10.32 RDNA) |
2025-10-29 |
|
CVE-2024-36325 |
AMD Software: Adrenalin Edition 25.10.2 |
2025-10-29 |
|
Radeon Software for Linux 24.20.3 |
2025-10-29 |
||
CVE-2025-66661 |
AMD Software: PRO Edition 25.Q3.1 (25.10.32 RDNA) |
2025-10-14 |
|
AMD Radeon™ PRO W5000 Series Graphics Products |
CVE-2026-0453 |
Radeon™ Software for Linux 26.14
|
2026-08-26
|
CVE-2025-0047 |
|||
CVE-2024-36313
|
AMD Software: Adrenalin Edition 26.7.1 |
2026-08-18 |
|
Radeon™ Software for Linux 26.14 |
2026-08-26 |
||
CVE-2026-0457 |
No fix planned1 |
N/A |
|
CVE-2026-40680 |
Radeon™ Software for Linux 26.13 |
2026-07-20 |
|
CVE-2026-0439 |
AMD Software: Adrenalin Edition 26.6.1 |
2026-06-02 |
|
CVE-2026-0445 |
|||
CVE-2026-0449 |
|||
CVE-2026-0469 |
|||
CVE-2024-21940 |
Radeon Software for Linux 26.12 |
2026-05-20 |
|
CVE-2026-0423 |
|||
CVE-2026-0425 |
|||
CVE-2026-0463 |
|||
CVE-2026-0464 |
|||
CVE-2026-28236 |
|||
CVE-2026-40673 |
|||
CVE-2026-0443 |
AMD Software: Adrenalin Edition 26.5.2 |
2026-05-14 |
|
CVE-2026-0446 |
|||
CVE-2026-0471 |
AMD Software: Adrenalin Edition 26.5.2 |
2026-05-14 |
|
CVE-2026-0477 |
|||
CVE-2026-0478 |
|||
CVE-2026-0479 |
|||
CVE-2026-0440 |
AMD Software: Adrenalin Edition 26.3.1 |
2026-03-19 |
|
CVE-2026-0442 |
|||
CVE-2026-0444 |
|||
CVE-2026-0447 |
|||
CVE-2026-0472 |
|||
CVE-2024-21940 |
AMD Software: PRO Edition 26.Q1 (25.10.41.01 RDNA) |
2026-01-21 |
|
CVE-2026-0448 |
|||
CVE-2026-0452 |
|||
CVE-2026-0468 |
|||
CVE-2025-62622 |
AMD Software: PRO Edition 25.Q4 (25.10.37.01) |
2025-12-11 |
|
CVE-2025-66662 |
|||
CVE-2026-0451 |
|||
CVE-2025-66663 |
AMD Software: PRO Edition 25.Q3.1 (25.10.32) |
2025-11-13 |
|
CVE-2024-36317 |
AMD Software: PRO Edition 25.Q3.1 (25.10.32 RDNA) |
2025-10-29 |
|
CVE-2024-36325 |
|||
CVE-2025-66661 |
|||
CVE-2024-36344 |
AMD Software: PRO Edition 25.Q2 (25.10.10) |
2025-06-03 |
|
AMD Radeon™ PRO W6000 Series Graphics Products |
CVE-2026-0453 |
Radeon™ Software for Linux 26.14 |
2026-08-26 |
CVE-2025-0047 |
|||
CVE-2024-36313 |
Radeon™ Software for Linux 26.14 |
2026-08-26 |
|
AMD Software: Adrenalin Edition 26.7.1 |
2026-08-18 |
||
CVE-2026-0457 |
No fix planned1 |
N/A |
|
CVE-2026-40680 |
Radeon™ Software for Linux 26.13 |
2026-07-20 |
|
CVE-2026-0439 |
AMD Software: Adrenalin Edition 26.6.1 |
2026-06-02 |
|
CVE-2026-0445 |
|||
CVE-2026-0449 |
|||
CVE-2026-0469 |
|||
CVE-2024-21940 |
Radeon Software for Linux 26.12 |
2026-05-20 |
|
CVE-2026-0002 |
|||
CVE-2026-0423 |
|||
CVE-2026-0425 |
|||
CVE-2026-0463 |
|||
CVE-2026-0464 |
|||
CVE-2026-28236 |
|||
CVE-2026-40673 |
|||
CVE-2026-0443 |
AMD Software: Adrenalin Edition 26.5.2 |
2026-05-14 |
|
CVE-2026-0446 |
|||
CVE-2026-0471 |
AMD Software: Adrenalin Edition 26.5.2 |
2026-05-14 |
|
CVE-2026-0477 |
|||
CVE-2026-0478 |
|||
CVE-2026-0479 |
|||
CVE-2026-0002 |
AMD Software: Adrenalin Edition 26.3.1 |
2026-03-19 |
|
CVE-2026-0440 |
|||
CVE-2026-0442 |
|||
CVE-2026-0444 |
|||
CVE-2026-0447 |
|||
CVE-2026-0472 |
|||
CVE-2024-21940 |
AMD Software: PRO Edition 26.Q1 (25.10.41.01 RDNA) |
2026-01-21 |
|
CVE-2026-0448 |
|||
CVE-2026-0452 |
|||
CVE-2026-0468 |
|||
CVE-2025-62622 |
AMD Software: PRO Edition 25.Q4 (25.10.37.01) |
2025-12-11 |
|
CVE-2025-66662 |
|||
CVE-2026-0451 |
|||
CVE-2025-66663 |
AMD Software: PRO Edition 25.Q3.1 (25.10.32) |
2025-11-13 |
|
AMD Software: PRO Edition 25.Q4 (25.10.37.01) |
2025-11-13 |
||
CVE-2024-36317 |
AMD Software: PRO Edition 25.Q3.1 (25.10.32 RDNA) |
2025-10-29 |
|
CVE-2024-36325 |
|||
CVE-2025-66661 |
|||
CVE-2024-36344 |
AMD Software: PRO Edition 25.Q2 (25.10.10) |
2025-06-03 |
|
AMD Radeon™ PRO W7000 Series Graphics Products |
CVE-2026-0453 |
Radeon™ Software for Linux 26.14 |
2026-08-26 |
CVE-2025-0047 |
AMD Software: Adrenalin Edition 26.7.1 |
2026-08-18 |
|
Radeon™ Software for Linux 26.14 |
2026-08-26 |
||
CVE-2024-36313 |
AMD Software: Adrenalin Edition 26.7.1 |
2026-08-18 |
|
Radeon™ Software for Linux 26.14 |
2026-08-26 |
||
CVE-2026-0457 |
No fix planned1 |
N/A |
|
CVE-2026-40680 |
Radeon™ Software for Linux 26.13 |
2026-07-20 |
|
CVE-2026-0439 |
AMD Software: Adrenalin Edition 26.6.1 |
2026-06-02 |
|
CVE-2026-0445 |
|||
CVE-2026-0449 |
|||
CVE-2026-0469 |
|||
CVE-2024-21940 |
Radeon Software for Linux 26.12 |
2026-05-20 |
|
CVE-2026-0002 |
|||
CVE-2026-0422 |
|||
CVE-2026-0423 |
|||
CVE-2026-0425 |
|||
CVE-2026-0463 |
|||
CVE-2026-0464 |
|||
CVE-2026-28236 |
|||
CVE-2026-40673 |
|||
CVE-2026-0443 |
AMD Software: Adrenalin Edition 26.5.2 |
2026-05-14 |
|
CVE-2026-0446 |
|||
CVE-2026-0002 |
AMD Software: Adrenalin Edition 26.3.1 |
2026-03-19 |
|
CVE-2026-0440 |
|||
CVE-2026-0442 |
|||
CVE-2026-0444 |
|||
CVE-2026-0447 |
|||
CVE-2026-0471 |
Adrenalin Edition 26.3.1 |
2026-03-19 |
|
CVE-2026-0472 |
AMD Software: Adrenalin Edition 26.3.1 |
2026-03-19 |
|
CVE-2026-0477 |
AMD Software: Adrenalin Edition 26.3.1 |
2026-03-19 |
|
CVE-2026-0478 |
|||
CVE-2026-0479 |
|||
CVE-2024-21940 |
AMD Software: PRO Edition 26.Q1 (25.10.41.01 RDNA) |
2026-01-21 |
|
CVE-2026-0448 |
|||
CVE-2026-0452 |
|||
CVE-2026-0468 |
|||
CVE-2025-62622 |
AMD Software: PRO Edition 25.Q4 (25.10.37.01) |
2025-12-11 |
|
CVE-2025-66662 |
|||
CVE-2026-0451 |
|||
CVE-2025-66663 |
AMD Software: PRO Edition 25.Q3.1 (25.10.32) |
2025-11-13 |
|
CVE-2026-0459 |
ROCm 7.1 |
2025-10-30 |
|
CVE-2024-36317 |
AMD Software: PRO Edition 25.Q3.1 (25.10.32 RDNA) |
2025-10-29 |
|
CVE-2024-36325 |
|||
CVE-2025-66661 |
|||
CVE-2024-36344 |
AMD Software: PRO Edition 25.Q2 (25.10.10) |
2025-06-03 |
|
AMD Radeon™ PRO W9000 Series Graphics Products |
CVE-2026-0457 |
No fix planned1 |
N/A |
AMD Radeon™ RX 5000 Series Graphics Products |
CVE-2026-0453 |
Radeon™ Software for Linux 26.14
|
2026-08-26
|
CVE-2024-36313 |
|||
CVE-2025-0047 |
|||
CVE-2026-0457 |
No fix planned1 |
N/A |
|
CVE-2026-40680 |
Radeon™ Software for Linux 26.13 |
2026-07-20 |
|
CVE-2026-0439 |
AMD Software: Adrenalin Edition 26.6.1 |
2026-06-02 |
|
CVE-2026-0445 |
|||
CVE-2026-0449 |
|||
CVE-2026-0469 |
|||
CVE-2024-21940 |
Radeon Software for Linux 26.12 |
2026-05-20 |
|
CVE-2026-0423 |
|||
CVE-2026-0425 |
|||
CVE-2026-0463 |
|||
CVE-2026-0464 |
|||
CVE-2026-28236 |
|||
CVE-2026-40673 |
|||
CVE-2026-0443 |
AMD Software: Adrenalin Edition 26.5.2 |
2026-05-14 |
|
CVE-2026-0446 |
|||
CVE-2026-0471 |
AMD Software: Adrenalin Edition 26.5.2 |
2026-05-14 |
|
CVE-2026-0477 |
|||
CVE-2026-0478 |
|||
CVE-2026-0479 |
|||
CVE-2026-0440 |
AMD Software: Adrenalin Edition 26.3.1 |
2026-03-19 |
|
CVE-2026-0442 |
|||
CVE-2026-0444 |
|||
CVE-2026-0447 |
|||
CVE-2026-0472 |
|||
CVE-2024-21940 |
AMD Software: Adrenalin Edition 26.1.1 |
2026-01-21 |
|
CVE-2026-0448 |
|||
CVE-2026-0452 |
|||
CVE-2026-0468 |
|||
CVE-2025-62622 |
AMD Software: Adrenalin Edition 25.12.1 (25.10.37.01) |
2025-12-10 |
|
CVE-2025-66662 |
|||
CVE-2026-0451 |
|||
CVE-2025-66663 |
AMD Software: Adrenalin Edition 25.11.1 (25.10.33.03) |
2025-11-13 |
|
CVE-2024-36317 |
AMD Software: Adrenalin Edition 25.10.2 |
2025-10-29 |
|
CVE-2024-36325 |
|||
Radeon Software for Linux 24.20.3 |
2025-10-29 |
||
CVE-2025-66661 |
AMD Software: Adrenalin Edition 25.10.2 |
2025-10-29 |
|
CVE-2024-36344 |
AMD Software: Adrenalin Edition 25.5.1 (25.10.01.09) |
2025-06-03 |
|
AMD Radeon™ RX 6000 Series Graphics Products |
CVE-2026-0453 |
Radeon™ Software for Linux 26.14 |
2026-08-26 |
CVE-2025-0047 |
AMD Software: Adrenalin Edition 26.7.1 |
2026-08-18 |
|
Radeon Software for Linux 26.14 |
2026-08-26 |
||
CVE-2024-36313
|
AMD Software: Adrenalin Edition 26.7.1 |
2026-08-18 |
|
Radeon Software for Linux 26.14 |
2026-08-26 |
||
CVE-2026-0457 |
No fix planned1 |
N/A |
|
CVE-2026-40680 |
Radeon™ Software for Linux 26.13 |
2026-07-20 |
|
CVE-2026-0439 |
AMD Software: Adrenalin Edition 26.6.1 |
2026-06-02 |
|
CVE-2026-0445 |
|||
CVE-2026-0449 |
|||
CVE-2026-0469 |
|||
CVE-2024-21940 |
Radeon Software for Linux 26.12 |
2026-05-20 |
|
CVE-2026-0002 |
|||
CVE-2026-0423 |
|||
CVE-2026-0425 |
|||
CVE-2026-0463 |
|||
CVE-2026-0464 |
|||
CVE-2026-28236 |
|||
CVE-2026-40673 |
|||
CVE-2026-0443 |
AMD Software: Adrenalin Edition 26.5.2 |
2026-05-14 |
|
CVE-2026-0446 |
|||
CVE-2026-0471 |
AMD Software: Adrenalin Edition 26.5.2 |
2026-05-14 |
|
CVE-2026-0477 |
|||
CVE-2026-0478 |
|||
CVE-2026-0479 |
|||
CVE-2026-0002 |
AMD Software: Adrenalin Edition 26.3.1 |
2026-03-19 |
|
CVE-2026-0440 |
|||
CVE-2026-0442 |
|||
CVE-2026-0444 |
|||
CVE-2026-0447 |
|||
CVE-2026-0472 |
|||
CVE-2024-21940 |
AMD Software: Adrenalin Edition 26.1.1 |
2026-01-21 |
|
AMD Software: PRO Edition 26.Q1 (25.10.41.01 RDNA) |
2026-01-21 |
||
CVE-2026-0448 |
AMD Software: Adrenalin Edition 26.1.1 |
2026-01-21 |
|
CVE-2026-0452 |
|||
CVE-2026-0468 |
|||
CVE-2025-66663 |
AMD Software: Adrenalin Edition 25.12.1 (25.10.37.01) |
2025-12-11 |
|
CVE-2025-62622 |
|||
CVE-2025-66662 |
|||
CVE-2026-0451 |
|||
CVE-2025-66663 |
AMD Software: Adrenalin Edition 25.11.1 (25.10.33.03) |
2025-11-13 |
|
CVE-2024-36317 |
AMD Software: Adrenalin Edition 25.10.2 |
2025-10-29 |
|
CVE-2024-36325 |
|||
Radeon Software for Linux 24.20.3 |
2025-10-29 |
||
CVE-2025-66661 |
AMD Software: Adrenalin Edition 25.10.2 |
2025-10-29 |
|
CVE-2024-36344 |
AMD Software: Adrenalin Edition 25.5.1 (25.10.01.09) |
2025-06-03 |
|
AMD Radeon™ RX 7000 Series Graphics Products |
CVE-2026-0453 |
Radeon™ Software for Linux 26.14 |
2026-08-26 |
CVE-2025-0047 |
AMD Software: Adrenalin Edition 26.7.1 |
2026-08-18 |
|
Radeon™ Software for Linux 26.14 |
2026-08-26 |
||
CVE-2024-36313 |
AMD Software: Adrenalin Edition 26.7.1 |
2026-08-18 |
|
Radeon™ Software for Linux 26.14 |
2026-08-26 |
||
CVE-2026-40680 |
Radeon™ Software for Linux 26.13 |
2026-07-20 |
|
CVE-2026-0457 |
No fix planned1 |
N/A |
|
CVE-2026-0439 |
AMD Software: Adrenalin Edition 26.6.1 |
2026-06-02 |
|
CVE-2026-0445 |
|||
CVE-2026-0449 |
|||
CVE-2026-0469 |
|||
CVE-2024-21940 |
Radeon Software for Linux 26.12 |
2026-05-20 |
|
CVE-2026-0002 |
|||
CVE-2026-0422 |
|||
CVE-2026-0423 |
|||
CVE-2026-0425 |
|||
CVE-2026-0463 |
|||
CVE-2026-0464 |
|||
CVE-2026-28236 |
|||
CVE-2026-40673 |
|||
CVE-2026-0443 |
AMD Software: Adrenalin Edition 26.5.2 |
2026-05-14 |
|
CVE-2026-0446 |
|||
CVE-2026-0471 |
Adrenalin Edition 26.3.1 (25.30.33.01 RDNA3+) |
2026-05-14 |
|
CVE-2026-0478 |
AMD Software: Adrenalin Edition 26.3.1 |
2026-05-14 |
|
CVE-2026-0479 |
|||
CVE-2026-0002 |
AMD Software: Adrenalin Edition 26.3.1 |
2026-03-19 |
|
CVE-2026-0440 |
|||
CVE-2026-0442 |
|||
CVE-2026-0444 |
|||
CVE-2026-0447 |
|||
CVE-2026-0472 |
|||
CVE-2026-0477 |
|||
CVE-2024-21940 |
AMD Software: Adrenalin Edition 26.1.1 |
2026-01-21 |
|
CVE-2026-0448 |
|||
CVE-2026-0452 |
|||
CVE-2026-0468 |
|||
CVE-2025-62622 |
AMD Software: Adrenalin Edition 25.12.1 (25.20.29.09) |
2025-12-10 |
|
CVE-2025-66662 |
|||
CVE-2026-0451 |
|||
CVE-2025-66663 |
AMD Software: Adrenalin Edition 25.11.1 (25.10.33.03) |
2025-11-13 |
|
CVE-2026-0459 |
ROCm 7.1 |
2025-10-30 |
|
CVE-2024-36317 |
AMD Software: Adrenalin Edition 25.10.2 |
2025-10-29 |
|
CVE-2024-36325 |
|||
Radeon Software for Linux 24.20.3 |
2025-10-29 |
||
CVE-2025-66661 |
AMD Software: Adrenalin Edition 25.10.2 (25.20.21.01 RDNA3+) |
2025-10-29 |
|
CVE-2024-36344 |
AMD Software: Adrenalin Edition 25.5.1 (25.10.01.09) |
2025-06-03 |
|
AMD Radeon™ RX 9000 Series Graphics Products |
CVE-2026-0453 |
Radeon™ Software for Linux 26.14 |
2026-08-26 |
CVE-2025-0047 |
AMD Software: Adrenalin Edition 26.7.1 |
2026-08-18 |
|
Radeon™ Software for Linux 26.14 |
2026-08-26 |
||
CVE-2024-36313
|
AMD Software: Adrenalin Edition 26.7.1 |
2026-08-18 |
|
Radeon™ Software for Linux 26.14 |
2026-08-26 |
||
CVE-2026-40680 |
Radeon™ Software for Linux 26.13 |
2026-07-20 |
|
CVE-2026-0457 |
No fix planned1 |
N/A |
|
CVE-2026-0439 |
AMD Software: Adrenalin Edition 26.6.1 |
2026-06-02 |
|
CVE-2026-0445 |
|||
CVE-2026-0449 |
|||
CVE-2026-0469 |
|||
CVE-2024-21940 |
Radeon Software for Linux 26.12 |
2026-05-20 |
|
CVE-2026-0002 |
|||
CVE-2026-0422 |
|||
CVE-2026-0423 |
|||
CVE-2026-0425 |
|||
CVE-2026-0463 |
|||
CVE-2026-0464 |
|||
CVE-2026-28236 |
|||
CVE-2026-40673 |
|||
CVE-2026-0443 |
AMD Software: Adrenalin Edition 26.5.2 |
2026-05-14 |
|
CVE-2026-0446 |
|||
CVE-2026-0002 |
AMD Software: Adrenalin Edition 26.3.1 |
2026-03-19 |
|
CVE-2026-0440 |
|||
CVE-2026-0442 |
|||
CVE-2026-0444 |
|||
CVE-2026-0447 |
|||
CVE-2026-0471 |
Adrenalin Edition 26.3.1 (25.30.33.01 RDNA3+) |
2026-03-19 |
|
CVE-2026-0472 |
AMD Software: Adrenalin Edition 26.3.1 |
2026-03-19 |
|
CVE-2026-0477 |
AMD Software: Adrenalin Edition 26.3.1 |
2026-03-19 |
|
CVE-2026-0478 |
|||
CVE-2026-0479 |
|||
CVE-2024-21940 |
AMD Software: Adrenalin Edition 26.1.1 |
2026-01-21 |
|
CVE-2026-0448 |
|||
CVE-2026-0452 |
|||
CVE-2026-0468 |
|||
CVE-2025-62622 |
AMD Software: Adrenalin Edition 25.12.1 (25.20.29.09) |
2025-12-10 |
|
CVE-2025-66662 |
|||
CVE-2026-0451 |
|||
CVE-2026-0459 |
ROCm 7.1 |
2025-10-30 |
|
CVE-2024-36317 |
AMD Software: Adrenalin Edition 25.10.2 |
2025-10-29 |
|
CVE-2024-36325 |
AMD Software: Adrenalin Edition 25.10.2 |
2025-10-29 |
|
Radeon Software for Linux 24.20.3 |
2025-10-29 |
||
CVE-2025-66661 |
AMD Software: PRO Edition 25.Q3.1 (25.10.32 RDNA) |
2025-10-14 |
1Restricting register access will break profilers.
AMD Radeon™ PRO V Series Graphics Products
Product |
CVE ID |
Mitigation |
AMD Radeon™ PRO V520 |
CVE-2026-0457 |
No fix planned1 |
CVE-2024-21940 |
Contact your AMD Customer Engineering representative |
|
CVE-2024-36313 |
||
CVE-2024-36317 |
||
CVE-2025-0047 |
||
CVE-2026-0425 |
||
CVE-2026-0439 |
||
CVE-2026-0440 |
||
CVE-2026-0442 |
||
CVE-2026-0443 |
||
CVE-2026-0445 |
||
CVE-2026-0446 |
||
CVE-2026-0449 |
||
CVE-2026-0452 |
||
CVE-2026-0453 |
||
CVE-2026-0463 |
||
CVE-2026-0468 |
||
CVE-2026-0469 |
||
CVE-2026-0471 |
||
CVE-2026-0472 |
||
CVE-2026-0477 |
||
CVE-2026-0478 |
||
CVE-2026-0479 |
||
CVE-2026-28236 |
||
CVE-2026-40673 |
||
CVE-2025-62622 |
||
CVE-2025-66661 |
||
CVE-2025-66662 |
||
CVE-2026-0451 |
||
CVE-2025-66663 |
||
CVE-2024-36325 |
||
CVE-2024-36344 |
||
AMD Radeon™ PRO V620 |
CVE-2026-0457 |
No fix planned1 |
CVE-2025-0047 |
Contact your AMD Customer Engineering representative |
|
CVE-2024-21940 |
||
CVE-2024-36313 |
||
CVE-2024-36325 |
||
CVE-2025-62622 |
||
CVE-2025-66661 |
||
CVE-2025-66662 |
||
CVE-2026-0002 |
||
CVE-2026-0425 |
||
CVE-2026-0439 |
||
CVE-2026-0440 |
||
CVE-2026-0442 |
||
CVE-2026-0443 |
||
CVE-2026-0444 |
||
CVE-2026-0445 |
||
CVE-2026-0446 |
||
CVE-2026-0447 |
||
CVE-2026-0448 |
||
CVE-2026-0449 |
||
CVE-2026-0451 |
||
CVE-2026-0452 |
||
CVE-2026-0453 |
||
CVE-2026-0459 |
||
CVE-2026-0463 |
||
CVE-2026-0464 |
||
CVE-2026-0468 |
||
CVE-2026-0469 |
||
CVE-2026-0471 |
||
CVE-2026-0472 |
||
CVE-2026-0477 |
||
CVE-2026-0478 |
||
CVE-2026-0479 |
||
CVE-2026-28236 |
||
CVE-2026-40673 |
||
CVE-2026-40680 |
||
CVE-2024-36317 |
||
CVE-2025-66663 |
||
CVE-2024-36344 |
||
AMD Radeon™ PRO V710
|
CVE-2026-0457 |
No fix planned1 |
CVE-2025-0047 |
Contact your AMD Customer Engineering representative
|
|
CVE-2024-21940 |
||
CVE-2024-36313 |
||
CVE-2024-36325 |
||
CVE-2025-62622 |
||
CVE-2025-66661 |
||
CVE-2025-66662 |
||
CVE-2026-0002 |
||
CVE-2026-0425 |
||
CVE-2026-0439 |
||
CVE-2026-0440 |
||
CVE-2026-0442 |
||
CVE-2026-0443 |
||
CVE-2026-0444 |
||
CVE-2026-0445 |
||
CVE-2026-0446 |
||
CVE-2026-0447 |
||
CVE-2026-0448 |
||
CVE-2026-0449 |
||
CVE-2026-0451 |
||
CVE-2026-0452 |
||
CVE-2026-0453 |
||
CVE-2026-0459 |
||
CVE-2026-0463 |
||
CVE-2026-0464 |
||
CVE-2026-0468 |
||
CVE-2026-0469 |
||
CVE-2026-0471 |
||
CVE-2026-0472 |
||
CVE-2026-0477 |
||
CVE-2026-0478 |
||
CVE-2026-0479 |
||
CVE-2026-28236 |
||
CVE-2026-40673 |
||
CVE-2026-40680 |
||
CVE-2025-66663 |
||
CVE-2024-36317 |
||
CVE-2024-36344 |
1 Restricting register access will break profilers.
AMD Instinct™ Accelerators
Product |
CVE ID |
Mitigation |
Mitigation Release Date |
AMD Instinct™ MI200 |
CVE-2025-66663 |
AMDGPU Driver 30.10 |
2025-09-16 |
AMD Instinct™ MI210 |
CVE-2026-0457 |
No fix planned1 |
N/A |
CVE-2026-40673 |
AMD GPU Kernel Driver 31.40 |
2026-07-15
|
|
CVE-2024-36313 |
|||
CVE-2026-40680 |
|||
CVE-2025-0047 |
|||
CVE-2026-0002 |
AMDGPU Driver 31.40 |
2026-07-15 |
|
CVE-2026-0426 |
AMD GPU Kernel Driver 31.30 |
2026-05-15 |
|
CVE-2026-0463 |
AMD GPU Kernel Driver 30.30.2 |
2026-04-17 |
|
CVE-2026-0423 |
AMD GPU Kernel Driver 31.20 |
2026-03-26 |
|
CVE-2026-0425 |
|||
CVE-2026-0464 |
|||
CVE-2026-28236 |
|||
CVE-2024-21940 |
AMD GPU Driver 30.30 |
2026-01-21 |
|
CVE-2026-0453 |
ROCm 7.2 |
2026-01-21 |
|
CVE-2026-0459 |
ROCm 7.1 |
2025-10-30 |
|
CVE-2024-36344 |
AMDGPU Driver 25.10 |
2025-04-11 |
|
CVE-2024-36325 |
AMDGPU Driver 30.10 |
2024-11-06 |
|
AMD Instinct™ MI250 |
CVE-2026-0457 |
No fix planned1 |
N/A |
CVE-2026-40673 |
AMD GPU Kernel Driver 31.40 |
2026-07-15
|
|
CVE-2026-40680 |
|||
CVE-2024-36313 |
|||
CVE-2025-0047 |
|||
CVE-2026-0002 |
AMDGPU Driver 31.40 |
2026-07-15 |
|
CVE-2026-0426 |
AMD GPU Kernel Driver 31.30 |
2026-05-15 |
|
CVE-2026-0463 |
AMD GPU Kernel Driver 30.30.2 |
2026-04-17 |
|
CVE-2026-0423 |
AMD GPU Kernel Driver 31.20 |
2026-03-26 |
|
CVE-2026-0425 |
|||
CVE-2026-0464 |
|||
CVE-2026-28236 |
|||
CVE-2024-21940 |
AMD GPU Driver 30.30 |
2026-01-21 |
|
CVE-2026-0453 |
ROCm 7.2 |
2026-01-21 |
|
CVE-2026-0459 |
ROCm 7.1 |
2025-10-30 |
|
CVE-2024-36344 |
AMDGPU Driver 25.10 |
2025-04-11 |
|
CVE-2024-36325 |
AMDGPU Driver 30.10 |
2024-11-06 |
|
AMD Instinct™ MI250X |
CVE-2026-40673 |
AMD GPU Kernel Driver 31.40
|
2026-07-15
|
CVE-2026-40680 |
|||
CVE-2026-0426 |
AMD GPU Kernel Driver 31.30 |
2026-06-19 |
|
CVE-2026-0463 |
AMD GPU Kernel Driver 30.30.2 |
2026-04-17 |
|
CVE-2026-0423 |
AMD GPU Kernel Driver 31.20 |
2026-03-26 |
|
CVE-2026-0425 |
|||
CVE-2026-0464 |
|||
CVE-2026-28236 |
|||
AMD Instinct™ MI300A |
CVE-2026-0457 |
No fix planned1 |
N/A |
CVE-2026-0456 |
PI100D |
2026-08-17 |
|
CVE-2026-40673 |
AMD GPU Kernel Driver 31.40
|
2026-07-15
|
|
CVE-2026-40680 |
|||
CVE-2024-36313 |
|||
CVE-2025-0047 |
|||
CVE-2026-0426 |
AMD GPU Kernel Driver 31.30 |
2026-06-19 |
|
CVE-2026-0463 |
AMD GPU Kernel Driver 30.30.2 |
2026-04-17 |
|
CVE-2026-0423 |
AMD GPU Kernel Driver 31.20 |
2026-03-26 |
|
CVE-2026-0425 |
|||
CVE-2026-0464 |
|||
CVE-2026-28236 |
|||
CVE-2024-21940 |
AMD GPU Driver 30.30 |
2026-01-21 |
|
CVE-2024-36317 |
AMD GPU Kernel Driver 30.30 |
2026-01-21 |
|
CVE-2026-0453 |
ROCm 7.2 |
2026-01-21 |
|
CVE-2026-0459 |
ROCm 7.1 |
2025-10-30 |
|
CVE-2024-36322 |
AMDGPU Driver 30.10 |
2025-09-16 |
|
CVE-2024-36344 |
AMDGPU Driver 25.10 |
2025-04-25 |
|
CVE-2024-36325 |
AMDGPU Driver 30.10 |
2024-11-06 |
|
AMD Instinct™ MI300X |
CVE-2026-0457 |
No fix planned1 |
N/A |
CVE-2026-0002 |
BKC 26.00 |
2026-08-07 |
|
CVE-2026-40673 |
AMD GPU Kernel Driver 31.40
|
2026-07-15
|
|
CVE-2026-40680 |
|||
CVE-2024-36313 |
|||
CVE-2025-0047 |
|||
CVE-2026-0456 |
AMDGPU Driver 31.40 |
2026-07-15 |
|
CVE-2026-0426 |
AMD GPU Kernel Driver 31.30 |
2026-06-19 |
|
CVE-2026-0463 |
AMD GPU Kernel Driver 30.30.2 |
2026-04-17 |
|
CVE-2026-0423 |
AMD GPU Kernel Driver 31.20 |
2026-03-26 |
|
CVE-2026-0425 |
|||
CVE-2026-0464 |
|||
CVE-2026-28236 |
|||
CVE-2024-21940 |
AMD GPU Driver 30.30 |
2026-01-21 |
|
CVE-2024-36317 |
AMD GPU Kernel Driver 30.30 |
2026-01-21 |
|
CVE-2026-0453 |
ROCm 7.2 |
2026-01-21 |
|
CVE-2026-0459 |
ROCm 7.1 |
2025-10-30 |
|
CVE-2024-36322 |
AMDGPU Driver 30.10 |
2025-09-16 |
|
CVE-2024-36344 |
AMDGPU Driver 25.10 |
2025-04-11 |
|
CVE-2024-36325 |
AMDGPU Driver 30.10 |
2024-11-06 |
|
AMD Instinct™ MI308 |
CVE-2026-0456 |
AMDGPU Driver 30.30 |
2026-02-13 |
CVE-2024-36344 |
AMDGPU Driver 25.10 |
2025-04-11 |
|
AMD Instinct™ MI308X |
CVE-2026-40673 |
AMD GPU Kernel Driver 31.40
|
2026-07-15
|
CVE-2026-40680 |
|||
CVE-2024-36313 |
|||
CVE-2025-0047 |
|||
CVE-2026-0426 |
AMD GPU Kernel Driver 31.30 |
2026-05-15 |
|
CVE-2026-0463 |
AMD GPU Kernel Driver 30.30.2 |
2026-04-17 |
|
CVE-2026-0423 |
AMD GPU Kernel Driver 31.20 |
2026-03-26 |
|
CVE-2026-0425 |
|||
CVE-2026-0464 |
|||
CVE-2026-28236 |
|||
CVE-2024-21940 |
AMD GPU Driver 30.30 |
2026-01-21 |
|
CVE-2024-36317 |
AMD GPU Kernel Driver 30.30 |
2026-01-21 |
|
CVE-2026-0453 |
ROCm 7.2 |
2026-01-21 |
|
CVE-2024-36322 |
AMDGPU Driver 30.10
|
2025-09-16
|
|
CVE-2024-36325 |
|||
AMD Instinct™ MI325X |
CVE-2026-0457 |
No fix planned1 |
N/A |
CVE-2026-40673 |
AMD GPU Kernel Driver 31.40
|
2026-07-15
|
|
CVE-2026-40680 |
|||
CVE-2024-36313 |
|||
CVE-2025-0047 |
|||
CVE-2026-0456 |
|||
CVE-2026-0426 |
AMD GPU Kernel Driver 31.30 |
2026-05-15 |
|
CVE-2026-0002 |
BKC 25.06.08 |
2026-04-17 |
|
CVE-2026-0463 |
AMD GPU Kernel Driver 30.30.2 |
2026-04-17 |
|
CVE-2026-0423 |
AMD GPU Kernel Driver 31.20 |
2026-03-26 |
|
CVE-2026-0425 |
|||
CVE-2026-0464 |
|||
CVE-2026-28236 |
|||
CVE-2024-21940 |
AMD GPU Driver 30.30 |
2026-01-21 |
|
CVE-2024-36317 |
AMD GPU Kernel Driver 30.30 |
2026-01-21 |
|
CVE-2026-0453 |
ROCm 7.2 |
2026-01-21 |
|
CVE-2026-0459 |
ROCm 7.1 |
2025-10-30 |
|
CVE-2024-36322 |
AMDGPU Driver 30.10 |
2025-09-16 |
|
CVE-2024-36344 |
AMDGPU Driver 25.10 |
2025-04-11 |
|
CVE-2024-36325 |
AMDGPU Driver 30.10 |
2024-11-06 |
|
AMD Instinct™ MI350 |
CVE-2026-0002 |
BKC 26.02 |
Target release planned for Nov’26 |
CVE-2024-36313 |
AMD GPU Kernel Driver 31.40 | 2026-07-15 | |
CVE-2026-0456 |
|||
CVE-2024-21940 |
AMD GPU Driver 30.30 |
2026-01-21 |
|
CVE-2026-0459 |
ROCm 7.1 |
2025-10-30 |
|
CVE-2024-36317 |
AMD GPU Kernel Driver 30.30 |
2025-09-16 |
|
AMD Instinct™ MI350X |
CVE-2026-40673 |
AMD GPU Kernel Driver 31.40 |
2026-07-15 |
CVE-2026-40680 |
|||
CVE-2025-0047 |
|||
CVE-2026-0426 |
AMD GPU Kernel Driver 31.30 |
2026-06-19 |
|
CVE-2026-0463 |
AMD GPU Kernel Driver 30.30.2 |
2026-04-17 |
|
CVE-2026-0423 |
AMD GPU Kernel Driver 31.20 |
2026-03-26 |
|
CVE-2026-0425 |
|||
CVE-2026-0464 |
|||
CVE-2026-28236 |
|||
CVE-2026-0453 |
ROCm 7.2 |
2026-01-21 |
|
AMD Instinct™ MI355 |
CVE-2026-0002 |
BKC 26.02 |
Target release planned for Nov'26 |
CVE-2024-36313 |
AMD GPU Kernel Driver 31.40 |
2026-07-15 |
|
CVE-2025-0047 |
|||
CVE-2026-0456 |
|||
CVE-2024-21940 |
AMD GPU Driver 30.30 |
2026-01-21 |
|
CVE-2026-0453 |
ROCm 7.2 |
2026-01-21 |
|
CVE-2026-0459 |
ROCm 7.1 |
2025-10-30 |
|
CVE-2024-36317 |
AMD GPU Kernel Driver 30.30 |
2025-09-16 |
|
AMD Instinct™ MI355X |
CVE-2026-40673 |
AMD GPU Kernel Driver 31.40
|
2026-07-15
|
CVE-2026-40680 |
|||
CVE-2026-0426 |
AMD GPU Kernel Driver 31.30 |
2026-06-19 |
|
CVE-2026-0463 |
AMD GPU Kernel Driver 30.30.2 |
2026-04-17 |
|
CVE-2026-0423 |
AMD GPU Kernel Driver 31.20 |
2026-03-26 |
|
CVE-2026-0425 |
|||
CVE-2026-0464 |
|||
CVE-2026-28236 |
1 Restricting register access will break profilers.
Acknowledgement
AMD thanks the following for reporting and engaging in coordinated vulnerability disclosure:
- Externally reported by Ben Rhoads of Meta Platforms, Inc: CVE-2026-0459
- Externally reported by JaeYeong LEE: CVE-2026-0422, CVE-2026-0423, CVE-2026-0426
- Externally reported by Cfir Cohen, Jann Horn, Mark Brand of Google: CVE-2025-66663
- Bug Bounty researcher Aobo Wang(@M4x_1997): CVE-2025-62622
- Bug Bounty researcher Sihyun Roh and Prof. Byoungyoung Lee, COMSEC Lab, Seoul National University: CVE-2026-40680
- Bug Bounty researcher Lei Lu and Ji'an Zhou: CVE-2026-0425, CVE-2026-0463, CVE-2026-0464, CVE-2026-28236, CVE-2026-40673
- Bug Bounty researcher Ming Shiang Tzou (@consolebreak): CVE-2025-66662
- Bug Bounty researcher "xnyuq": CVE-2026-0471, CVE-2026-0477, CVE-2026-0478, CVE-2026-0479
- Bug Bounty researcher "Ori Nimron (@orinimron123)": CVE-2025-66661, CVE-2026-0439, CVE-2026-0440, CVE-2026-0442, CVE-2026-0443, CVE-2026-0444, CVE-2026-0445, CVE-2026-0446, CVE-2026-0447, CVE-2026-0448, CVE-2026-0449, CVE-2026-0451, CVE-2026-0452, CVE-2026-0468, CVE-2026-0469, CVE-2026-0472
- Internally reported: CVE-2024-21940, CVE-2024-36313, CVE-2024-36317, CVE-2024-36322, CVE-2024-36325, CVE-2024-36344, CVE-2025-0047, CVE-2026-0002, CVE-2026-0453, CVE-2026-0456
Revisions
| Revision Date | Description |
| 2026-11-10 | Initial version |
DISCLAIMER
The information contained herein is for informational purposes only and is subject to change without notice. While every precaution has been taken in the preparation of this document, it may contain technical inaccuracies, omissions and typographical errors, and AMD is under no obligation to update or otherwise correct this information. Advanced Micro Devices, Inc. makes no representations or warranties with respect to the accuracy or completeness of the contents of this document, and assumes no liability of any kind, including the implied warranties of noninfringement, merchantability or fitness for particular purposes, with respect to the operation or use of AMD hardware, software or other products described herein. Any computer system has risks of security vulnerabilities that cannot be completely prevented or mitigated. No license, including implied or arising by estoppel, to any intellectual property rights is granted by this document. Terms and limitations applicable to the purchase or use of AMD's products are as set forth in a signed agreement between the parties or in AMD's Standard Terms and Conditions of Sale.
AMD, the AMD Arrow logo, Instinct, Radeon, and combinations thereof are trademarks of Advanced Micro Devices, Inc. CVE is a trademark of The MITRE Corporation. Other product names used in this publication are for identification purposes only and may be trademarks of their respective companies.
Third party content may be licensed to you directly by the third party that owns the content and is not licensed to you by AMD. ALL LINKED THIRD-PARTY CONTENT IS PROVIDED 'AS IS' WITHOUT A WARRANTY OF ANY KIND. USE OF SUCH THIRD-PARTY CONTENT IS DONE AT YOUR SOLE DISCRETION AND UNDER NO CIRCUMSTANCES WILL AMD BE LIABLE TO YOU FOR ANY THIRD PARTY CONTENT. YOU ASSUME ALL RISK AND ARE SOLELY RESPONSIBILITY FOR ANY DAMAGES THAT MAY ARISE FROM YOUR USE OF THIRD-PARTY CONTENT.
© 2026 Advanced Micro Devices, Inc. All rights reserved.