dbcve.org
Out-of-bounds WriteWeakness · CWE-787

CVE-2025-54517

HIGH · 8.5 CVSS v4.0 Published 2026-05-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
87/100
Remediation priority · High
Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

Out-of-bounds write vulnerability in the AMDGV_CMD_GET_DIAG_DATA ioctl handler within AMD's graphics virtualization driver. The memory corruption flaw allows a local attacker to write beyond allocated buffer boundaries, potentially achieving privilege escalation to execute code with elevated privileges.

MitigationApply the AMD vendor patch for the graphics virtualization driver; until patched, restrict local user access to systems with the vulnerable driver and monitor for exploitation attempts.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify if AMD graphics virtualization driver is loaded
    Check for amdgpu kernel module: lsmod | grep amdgpu, or check /sys/module/amdgpu/version if it exists
    Affected if The amdgpu module is loaded without the vendor patch applied to the AMDGV_CMD_GET_DIAG_DATA ioctl handler
  2. Determine the installed AMDGPU driver version
    Check /sys/module/amdgpu/version or run 'modinfo amdgpu' and look at the version field
    Affected if The driver version matches or falls within an unpatched version range for the graphics virtualization component
  3. Verify the presence of AMDGV ioctl interface
    Check for AMDGV-related device nodes or ioctl entry points: ls -la /dev/dri/* or check for amdgv-related entries in /proc or /sys
    Affected if The AMDGV_CMD_GET_DIAG_DATA ioctl interface exists and is accessible to local users
  4. Check for diagnostic data ioctl access permissions
    Review permissions on graphics device nodes and verify which local users have access to /dev/dri/cardX or related AMD virtualization interfaces
    Affected if Non-privileged local users can access the vulnerable ioctl handler interface

A system is affected if it runs an unpatched AMD graphics virtualization driver (amdgpu) with the AMDGV_CMD_GET_DIAG_DATA ioctl interface accessible to local users, allowing potential out-of-bounds memory writes for privilege escalation.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the AMD vendor patch for the graphics virtualization driver; until patched, restrict local user access to systems with the vulnerable driver and monitor for exploitation attempts.

Have this fixed Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA8.0 h
44.0 hours of engineering $7,720
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $12,352.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-54517 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-54517 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data