dbcve.org
Radeon SoftwareApplication · Amd

CVE-2020-12920

MEDIUM · 5.5 CVSS v3.1 Published 2021-11-15
Fix available
A fix is available. Upgrade to 20.11.2 or later.
See remediation →
57/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
A potential denial of service issue exists in the AMD Display driver Escape 0x130007 Call handler. An attacker with low privilege could potentially induce a Windows BugCheck.

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

A denial of service vulnerability exists in AMD Display Driver's Escape 0x130007 call handler where a low-privilege attacker can trigger a Windows BugCheck (Blue Screen of Death) by making a specific ioctl call.

MitigationApply the appropriate AMD display driver update from AMD's official support channels to remediate this vulnerability.

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
None
Integrity
None
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/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. Verify AMD Display Driver is installed
    Open Device Manager, expand 'Display adapters', and look for an AMD Radeon graphics device. Alternatively, open Programs and Features and search for AMD-related display driver entries.
    Affected if An AMD Radeon display adapter is present in the system
  2. Locate the AMD Radeon Software version
    Right-click the AMD Radeon Software icon in the system tray or desktop, select 'About' or 'Check for Updates' to view the version number. Alternatively, open Programs and Features, find the AMD Radeon Software entry, and note the version shown.
    Affected if The version displayed is less than 20.11.2
  3. Confirm driver version via command line
    Open Command Prompt and run 'wmic path win32_VideoController get name,driverversion' to retrieve the display driver version. Or use 'driverquery /v | findstr -i amd' to list AMD driver details.
    Affected if The driver version number is lower than 20.11.2
  4. Check for the vulnerable ioctl handler
    This step requires analyzing the driver file (atidxx64.dll or similar in the AMD driver directory) for the Escape 0x130007 handler presence. Use a hex editor or disassembler to inspect the driver if you have expertise, or review driver release notes for changes to ioctl handling.
    Affected if The driver is version 20.11.1 or earlier and contains the 0x130007 escape call handler

You are affected if AMD Radeon Software version 20.11.1 or earlier is installed, as the vulnerability exists in versions prior to 20.11.2.

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 appropriate AMD display driver update from AMD's official support channels to remediate this vulnerability.

Recommended fix High confidence

Radeon Software Adrenalin 2020 version 20.11.2

  1. 1. Visit the official AMD drivers and support page at www.amd.com/en/support
  2. 2. Select your graphics card product series and model
  3. 3. Choose Windows 10 (64-bit) as the operating system
  4. 4. Download the Radeon Software Adrenalin 2020 version 20.11.2 or later
  5. 5. Run the installer and follow the on-screen prompts
  6. 6. Restart the computer after installation completes
  7. 7. Verify the installed version by opening Radeon Software and checking the version number

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

Fix this in Radeon Software Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,800
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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