Enterprise DriverApplication · Amd

CVE-2020-12931

HIGH · 7.8 CVSS v3.1 Published 2022-11-09

Fix available

A fix is available. Upgrade to 22.q2 / 22.5.2 or later.

See remediation →

80/100

Remediation priority · High

Zero-click

Official description

NVD · unedited

Improper parameters handling in the AMD Secure Processor (ASP) kernel may allow a privileged attacker to elevate their privileges potentially leading to loss of integrity.

Technical summary

dbcve analysis · moderate confidence

This is a privilege escalation vulnerability in the AMD Secure Processor (ASP) kernel firmware. The vulnerability stems from improper parameter handling within the ASP kernel, allowing a privileged attacker to elevate their privileges beyond their intended boundaries, potentially leading to loss of integrity.

MitigationApply the AMD firmware update for the Secure Processor via BIOS/UEFI update from the system/OEM vendor. This typically requires updating the system BIOS to a version containing the patched ASP firmware.

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

Affected products & versions

NVD · CPE data

Enterprise DriverApplication

Affected:< 22.10.20

Radeon Pro SoftwareApplication

Affected:< 22.q2

Radeon SoftwareApplication

Affected:< 22.5.2

Ryzen 3 2200ge FirmwareOperating system

Affected:all versions

Ryzen 3 2200g FirmwareOperating system

Affected:all versions

Ryzen 5 2400ge FirmwareOperating system

Affected:all versions

Ryzen 5 2400g FirmwareOperating system

Affected:all versions

Ryzen 3 3100 FirmwareOperating system

Affected:all versions

CVSS breakdown

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?

dbcve checks

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

Identify CPU model

Run 'wmic cpu get name' on Windows or 'cat /proc/cpuinfo' on Linux to identify the processor model

Affected if The CPU model is Ryzen 3 2200G, Ryzen 3 2200GE, Ryzen 5 2400G, Ryzen 5 2400GE, or Ryzen 3 3100 - these have no fixed firmware patch available and are affected in all versions
Check AMD Secure Processor firmware version

On Windows, use 'wmic bios get version' or check BIOS/UEFI settings for 'AMD Secure Processor' or 'PSP' firmware version. On Linux, check 'dmesg' for AMD Secure Processor messages or use 'cpuid' to extract CPU information

Affected if The ASP firmware version cannot be determined to be 22.10.20 or later for the specific CPU model, indicating vulnerability
Check AMD Enterprise Driver version

Open Windows Device Manager, expand 'System devices', look for AMD Enterprise Driver and check the driver version in Properties, or run 'driverquery -v | findstr -i amd'

Affected if AMD Enterprise Driver version is installed and is earlier than 22.10.20
Check AMD Radeon Software version

Open AMD Radeon Software (usually in system tray or Start menu), click the gear icon, then 'About'. On Windows also check 'Programs and Features' for AMD Radeon Software version

Affected if AMD Radeon Software version is earlier than 22.5.2, indicating the driver component is vulnerable
Check AMD Radeon Pro Software version

Open AMD Radeon Pro Software or check 'Programs and Features' for the installed version

Affected if AMD Radeon Pro Software version is earlier than 22.q2, indicating the driver component is vulnerable

A system is affected if it contains any of the listed Ryzen CPU models (all firmware versions) or has AMD drivers/software older than the specified version thresholds.

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

Remediation

dbcve · scoped

Upgrade available Upgrade to 22.q2 / 22.5.2 / 22.10.20 or later

Fixed in 22.q222.5.222.10.20

Interim mitigation

Apply the AMD firmware update for the Secure Processor via BIOS/UEFI update from the system/OEM vendor. This typically requires updating the system BIOS to a version containing the patched ASP firmware.

Recommended fix Moderate confidence

Radeon Software >= 22.5.2, Radeon Pro Software >= 22.q2, Enterprise Driver >= 22.10.20, or OEM-provided BIOS/UEFI update containing ASP fix

1. Identify the specific AMD product in use from the affected list (Enterprise Driver, Radeon Pro Software, Radeon Software, or Ryzen APU firmware)
2. For AMD Software/Drivers: Navigate to amd.com/support and download the appropriate updated driver version (Radeon Software >= 22.5.2, Radeon Pro Software >= 22.q2, or Enterprise Driver >= 22.10.20)
3. Uninstall the current AMD software/driver completely before installing the updated version
4. Restart the system after driver installation completes
5. For Ryzen APU firmware (2200G, 2200GE, 2400G, 2400GE, 3100): Check with the original equipment manufacturer (OEM) or system builder for available BIOS/UEFI updates that include the AMD Secure Processor fix

Caveat Firmware updates carry risk and should be done with stable power; older Ryzen APUs may have limited BIOS update support from OEMs

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

Fix this in Enterprise Driver Scoped from the published advisory

Consultation4.0 h
Implementation3.0 h
Testing3.0 h
Review / QA2.0 h

12.0 hours of engineering $2,150

Get the upgrade done

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

Scan for this in your stack

Free · runs locally

dbcve dependency scanner

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

Primary sources

www.amd.comVendor Advisory
www.amd.com
nvd.nist.govNVD record

Practitioner notes

Contributed

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

Notes0 Guidelines

Know something about CVE-2020-12931?

The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.

The version that genuinely resolved it — not the one the vendor claimed
A config change or rule that shut the vector down
A gotcha in the upgrade path that cost you an afternoon

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

At a glance

A fix existsUpgrade to 22.q2 / 22.5.2 or later

Severity 7.8 High

Exploit likelihood EPSS, next 30 days 0.3%

Affects: Enterprise Driver

Remediation

A high-priority fix

Fix this in Enterprise Driver 12 hrs · Moderate

Typical engagement from $2,150

Get a fix See the full breakdown ↓

A high-priority vulnerability. Send your environment and a specialist will scope CVE-2020-12931 and return a fixed quote and timeline.

You’ll deal with our team directly and deploy the reviewed fix to staging first — never straight to production.

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.

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.

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.

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.

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.

Check your environment

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.

Scan for this in your stack

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

Practitioner notes

No notes yet

Official description

Technical summary

Affected products & versions

CVSS breakdown

Am I affected?

Remediation

References