dbcve.org
Radeon SoftwareApplication · Amd

CVE-2020-12893

HIGH · 7.8 CVSS v3.1 Published 2021-11-15
Fix available
A fix is available. Upgrade to 20.11.2 or later.
See remediation →
80/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
Stack Buffer Overflow in AMD Graphics Driver for Windows 10 in Escape 0x15002a may lead to escalation of privilege 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 · high confidence

A stack buffer overflow vulnerability exists in AMD Graphics Drivers for Windows 10 within the Escape function 0x15002a. This escape call, used for communication between user-mode applications and the kernel-mode graphics driver, fails to properly validate input buffer sizes before copying data to a stack-allocated buffer. A local attacker can trigger this overflow to execute arbitrary code in kernel context or cause a denial of service through system crash.

MitigationApply the latest AMD graphics driver update from AMD's official support channels. This vulnerability is addressed through driver patches that implement proper bounds checking on the Escape 0x15002a input parameters.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Radeon SoftwareApplication
Affected:< 20.11.2

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
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

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 installed AMD graphics driver version
    Open Command Prompt and run: wmic path win32_VideoController get name,driverversion. This displays the graphics card name and driver version installed on the system.
    Affected if The driver version shown is lower than 20.11.2 and the driver is AMD Radeon Software for Windows 10.
  2. Verify Windows 10 is the operating system
    Run: winver or systeminfo | findstr /B /C:"OS Name". Confirm the system is running Windows 10.
    Affected if The system is running Windows 10. The CVE specifically applies to Windows 10 environments.
  3. Confirm the driver is from AMD Radeon Software product line
    Check Device Manager under Display adapters. Look for AMD Radeon graphics adapters such as AMD Radeon RX series, AMD Radeon R series, or AMD Radeon Vega series.
    Affected if The displayed adapter is an AMD Radeon GPU and the associated driver version is below 20.11.2.

A system is affected if it runs Windows 10 with an AMD Radeon Graphics Driver version installed that is lower than 20.11.2, since the stack buffer overflow in Escape function 0x15002a exists in those older driver versions.

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.

dbcve · scoped
Upgrade available Upgrade to 20.11.2 or later
Fixed in 20.11.2
Interim mitigation

Apply the latest AMD graphics driver update from AMD's official support channels. This vulnerability is addressed through driver patches that implement proper bounds checking on the Escape 0x15002a input parameters.

Recommended fix High confidence

Radeon Software version 20.11.2 or later

  1. Check the current version of Radeon Software installed on the system (via AMD Radeon Settings or Programs and Features)
  2. Navigate to the official AMD support website at www.amd.com to download the latest Radeon Software driver package
  3. Download and install Radeon Software version 20.11.2 or later (the first fixed release)
  4. Restart the system to ensure the new graphics driver is fully loaded and active
  5. Verify the installed driver version matches or exceeds 20.11.2 after restart
Caveat Driver updates may temporarily affect display settings or require reconfiguration of custom graphics preferences; ensure backup of current settings if needed

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Radeon Software Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,210
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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