dbcve.org
Enterprise DriverApplication · Amd

CVE-2021-26360

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 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
An attacker with local access to the system can make unauthorized modifications of the security configuration of the SOC registers. This could allow potential corruption of AMD secure processor’s encrypted memory contents which may lead to arbitrary code execution in ASP.

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

CVE-2021-26360 is a local privilege escalation vulnerability in AMD processors where an attacker with local system access can make unauthorized modifications to SOC (System-on-Chip) register security configurations. This allows corruption of the AMD Secure Processor (ASP) encrypted memory contents, potentially enabling arbitrary code execution within the secure processor firmware.

MitigationApply AMD-provided firmware/BIOS updates that address this vulnerability. Organizations should identify affected AMD processor systems, obtain the latest firmware from AMD, and deploy through controlled update procedures.

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
Enterprise DriverApplication
Affected:< 22.10.20
Radeon Pro SoftwareApplication
Affected:< 22.q2
Radeon SoftwareApplication
Affected:< 22.5.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 the AMD processor and system type
    Use system information tools (such as systeminfo on Windows or lscpu/cpuinfo on Linux) to confirm the presence of an AMD processor in the system
    Affected if The system does not have an AMD processor - this vulnerability only affects AMD systems
  2. Check AMD Enterprise Driver version
    Locate and inspect the installed AMD Enterprise Driver version on the system, typically found in installed programs or driver details
    Affected if Installed version is earlier than 22.10.20
  3. Check AMD Radeon Pro Software version
    Locate and inspect the installed AMD Radeon Pro Software version, typically found in the software's about or help section
    Affected if Installed version is earlier than 22.q2 (for example, 22.q1 or earlier)
  4. Check AMD Radeon Software version
    Locate and inspect the installed AMD Radeon Software version, typically found in the software's about or help section
    Affected if Installed version is earlier than 22.5.2
  5. Verify AMD Secure Processor presence
    Check system BIOS/UEFI settings or use AMD diagnostic tools to determine if the AMD Secure Processor (ASP) feature is present and enabled on the system
    Affected if AMD Secure Processor is present and enabled - the vulnerability enables unauthorized modifications to its security configurations

The system is affected if it uses an AMD processor with any of the listed software/driver versions below the affected thresholds and has the AMD Secure Processor feature enabled.

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 22.q2 / 22.5.2 / 22.10.20 or later
Fixed in 22.q222.5.222.10.20
Interim mitigation

Apply AMD-provided firmware/BIOS updates that address this vulnerability. Organizations should identify affected AMD processor systems, obtain the latest firmware from AMD, and deploy through controlled update procedures.

Recommended fix High confidence

Enterprise Driver: 22.10.20 | Radeon Pro Software: 22.q2 | Radeon Software: 22.5.2

  1. Identify the AMD software product installed on the system (Enterprise Driver, Radeon Pro Software, or Radeon Software)
  2. Determine the current installed version of the software via the system's software management utility or AMD's version information
  3. For Enterprise Driver users: Upgrade to version 22.10.20 or later
  4. For Radeon Pro Software users: Upgrade to version 22.q2 or later
  5. For Radeon Software users: Upgrade to version 22.5.2 or later
  6. Obtain the appropriate updated driver/software from the official AMD website (www.amd.com) or through your organization's software distribution channel
  7. Apply the update following AMD's standard installation procedure
  8. Verify the installation was successful by confirming the updated version number
Caveat Review release notes for any driver compatibility changes with specific hardware configurations before upgrading

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
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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