AMD EPYC™ and EPYC™ Embedded Series Processors with Integrated Graphics
Summary
Potential vulnerabilities were reported that could impact some AMD EPYC™ and AMD EPYC™ Embedded Processors with Integrated Graphics. 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-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-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-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-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-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-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-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-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-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-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. |
CVSS:4.0: 6.2 |
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 SME |
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 EPYC™ Series Processors
AMD EPYC™ Series Processors
Product |
CVE ID |
Mitigation |
Mitigation Release Date |
AMD EPYC™ 4004 Series Processors |
CVE-2024-36313 |
AMD Software: Adrenalin Edition 26.7.1 |
2026-08-26 |
CVE-2026-0453 |
AMD Software: Adrenalin Edition 26.7.1 |
2026-08-18 |
|
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-0422 |
Radeon Software for Linux 26.12 |
2026-05-20 |
|
CVE-2026-0423 |
|||
CVE-2026-0425 |
|||
CVE-2026-0002 |
AMD Software: Adrenalin Edition 26.3.1 |
2026-05-14 |
|
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-0472 |
|||
CVE-2026-0448 |
AMD Software: Adrenalin Edition 26.1.1 |
2026-01-21 |
|
CVE-2025-62622 |
AMD Software: Adrenalin Edition 25.12.1 |
2025-12-10 |
|
CVE-2025-66662 |
|||
CVE-2026-0451 |
|||
CVE-2024-36317 |
AMD Software: Adrenalin Edition 25.10.2 |
2025-10-29 |
|
CVE-2025-66661 |
AMD Software: Adrenalin Edition 25.10.2 |
2025-10-29 |
|
AMD EPYC™ 4005 Series Processors |
CVE-2024-36313 |
AMD Software: Adrenalin Edition 26.7.1 |
2026-08-26 |
CVE-2026-0453 |
AMD Software: Adrenalin Edition 26.7.1 |
2026-08-18 |
|
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-0002 |
AMD Software: Adrenalin Edition 26.3.1 |
2026-05-20 |
|
CVE-2026-0422 |
Radeon Software for Linux 26.12 |
2026-05-20 |
|
CVE-2026-0423 |
|||
CVE-2026-0425 |
|||
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-0472 |
|||
CVE-2026-0448 |
AMD Software: Adrenalin Edition 26.1.1 |
2026-01-21 |
|
CVE-2025-62622 |
AMD Software: Adrenalin Edition 25.12.1 |
2025-12-10 |
|
CVE-2025-66662 |
|||
CVE-2026-0451 |
|||
CVE-2024-36317 |
AMD Software: Adrenalin Edition 25.10.2 |
2025-10-29 |
|
CVE-2025-66661 |
AMD Software: Adrenalin Edition 25.10.2 |
2025-10-29 |
AMD EPYC™ Embedded Series Processors
Product |
CVE ID |
Mitigation |
Mitigation Release Date |
AMD EPYC™ Embedded 4005 Series Processors |
CVE-2026-0453 |
Version TBD |
Target release planned for Dec'26 |
CVE-2026-0423 |
AMD Ubuntu 26.04 Distro Kernel(V7.0) |
2026-09-30 |
|
CVE-2026-40680 |
AMD Ubuntu 26.04 Distro Kernel(V7.0) |
2026-09-30 |
|
CVE-2026-0422 |
AMD Ubuntu 26.04 Distro Kernel(V7.0) |
2026-09-30 |
Acknowledgement
AMD thanks the following for reporting and engaging in coordinated vulnerability disclosure:
- 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
- Bug Bounty researcher "xnyuq": CVE-2026-0471, CVE-2026-0477, CVE-2026-0478, CVE-2026-0479
- Bug Bounty researcher JaeYeong LEE: CVE-2026-0422, CVE-2026-0423
- Bug Bounty researcher "Ori Nimron (@orinimron123)": CVE-2025-66661, CVE-2026-0439, CVE-2026-0440, CVE-2026-0448, CVE-2026-0451, CVE-2026-0472
- Bug Bounty researcher Ming Shiang Tzou (@consolebreak): CVE-2025-66662
- Bug Bounty researcher Aobo Wang(@M4x_1997): CVE-2025-62622
- Internally reported: CVE-2024-36313, CVE-2024-36317, CVE-2026-0002, CVE-2026-0453
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, EPYC, 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.