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

CVE-2025-48518

MEDIUM · 6.9 CVSS v4.0 Published 2026-02-11
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
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
Improper input validation in AMD Graphics Driver could allow a local attacker to write out of bounds, potentially resulting in loss of integrity or denial of service.

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

Improper input validation in AMD Graphics Driver allows a local attacker to perform out-of-bounds memory writes, potentially leading to loss of data integrity or system denial of service.

MitigationApply AMD's security updates for the graphics driver when released; until then, restrict local access to trusted users only.

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:N/VI:L/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 Driver is installed
    On Windows: Open Device Manager, expand 'Display adapters', check for AMD GPU and right-click for Properties > Driver tab. On Linux: Run 'lspci | grep -i amd' or check /usr/bin/ for amdgpu files. Also check Program Files/Program Files (x86) for AMD folder.
    Affected if No AMD GPU or AMD driver software is present on the system - not affected.
  2. Determine the installed AMD Graphics Driver version
    Windows: Device Manager > Display adapters > AMD GPU > Properties > Driver tab - note the Driver Version. Also check 'C:\Windows\System32\drivers\atikmdag.sys' file version. Linux: Run 'cat /sys/class/drm/card0/device/driver_version' or check 'amdvlk' package version.
    Affected if Driver version matches or falls within the affected version range published by AMD for this CVE.
  3. Verify if the vulnerable input validation component is in use
    AMD graphics drivers expose kernel-mode interfaces for user-mode applications. Check running graphics-intensive applications or check AMD driver settings/control panel for enabled features. On Windows, monitor for amdkfd or atikmdag driver activity.
    Affected if Any graphics application or compute workload using the AMD driver is active, enabling the attack surface.
  4. Check system access controls for local attack vector
    Review local user accounts, terminal services, and remote desktop settings. Ensure untrusted local users cannot execute code or access the graphics driver interfaces. Check 'who' and 'w' on Linux, or User Accounts in Windows Control Panel.
    Affected if Multiple local users exist with untrusted accounts, or remote desktop/terminal services allow access from untrusted users.

The system is affected if it runs an AMD Graphics Driver version within the CVE-affected range and has the driver or related graphics features actively in use by any user or application.

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 AMD's security updates for the graphics driver when released; until then, restrict local access to trusted users only.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,600
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-48518 — 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-48518 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