Quick answers
- Is CVE-2025-54517 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2025-54517 being exploited in the wild.
- How severe is CVE-2025-54517?
- Informational severity, with a CVSS score of 8.5, published 15 May 2026.
- Which products and versions are affected?
- AMD Graphics Driver.
- Is there a fix for CVE-2025-54517?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2025-54517 attacked?
- It is attacked with local access, in an operating system.
- Am I affected by CVE-2025-54517?
- Check whether you run Amd Graphics Driver. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
An out-of-bounds (OOB) write vulnerability exists within the AMDGV_CMD_GET_DIAG_DATA ioctl handler of the AMD graphics driver. The flaw is categorized as CWE-787 and occurs when the handler fails to properly validate buffer boundaries during diagnostic data retrieval. A local attacker with low privileges can trigger this vulnerability by sending a specially crafted ioctl request. Successful exploitation allows the attacker to overwrite memory, potentially leading to local privilege escalation (LPE) or arbitrary code execution in the context of the kernel or a high-privileged service.
Affected products
- AMD Graphics Driver
Timeline
- 2026-05-15: disclosed: Initial public disclosure by AMD and NVD.