dbcve.org
Radeon SoftwareApplication · Amd

CVE-2020-12904

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
Out of Bounds Read in AMD Graphics Driver for Windows 10 in Escape 0x3004203 may lead to arbitrary information disclosure.

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 read vulnerability in AMD graphics driver for Windows 10 in escape function 0x3004203 allows reading beyond allocated buffer boundaries, potentially exposing sensitive memory contents to an attacker.

MitigationApply AMD driver updates when available; until then, restrict access to untrusted users and monitor for attempts to exploit the vulnerable escape function.

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

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

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 Radeon Software is installed
    Open Programs and Features in Control Panel or use 'Get-ItemProperty HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\* | Select-Object DisplayName, DisplayVersion' in PowerShell to list installed programs and look for AMD Radeon Software entries
    Affected if AMD Radeon Software appears in the installed programs list
  2. Check AMD graphics driver version
    Open Device Manager, expand 'Display adapters', right-click on AMD GPU and select Properties, go to the Driver tab to view the driver version, or run 'Get-WmiObject Win32_VideoController | Select-Object Name, DriverVersion' in PowerShell
    Affected if Driver version is present and less than 20.11.2
  3. Confirm Windows 10 is the operating system
    Run 'winver' from the Run dialog or use 'Get-ComputerInfo | Select-Object OsName, OsVersion' in PowerShell
    Affected if Operating system is Windows 10 and AMD driver version is below 20.11.2
  4. Identify the specific escape function context
    This vulnerability exists in the kernel-mode graphics driver component. Check the driver file version of atiumdag.dll, atiumdva.dll, or similar AMD driver DLLs in C:\Windows\System32\drivers\ using 'Get-ItemProperty' to view version info
    Affected if AMD driver DLLs exist with versions corresponding to Radeon Software earlier than 20.11.2

The environment is affected if AMD Radeon Software or AMD graphics drivers for Windows 10 are installed with a version number lower than 20.11.2, as the vulnerable escape function 0x3004203 exists in those older driver releases.

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 AMD driver updates when available; until then, restrict access to untrusted users and monitor for attempts to exploit the vulnerable escape function.

Recommended fix High confidence

Radeon Software 20.11.2

  1. Open AMD Radeon Software on your Windows 10 system
  2. Navigate to the Settings or Preferences section
  3. Look for an option to check for updates or update the driver
  4. Alternatively, visit the official AMD website at www.amd.com and navigate to the Drivers & Support section
  5. Download Radeon Software version 20.11.2 or later for your specific GPU model
  6. Run the installer and follow the on-screen prompts to complete the upgrade
  7. Restart your computer after the installation completes

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
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
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,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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