dbcve.org
Enterprise DriverApplication · Amd

CVE-2021-26391

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
Insufficient verification of multiple header signatures while loading a Trusted Application (TA) may allow an attacker with privileges to gain code execution in that TA or the OS/kernel.

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

Insufficient signature verification in the Trusted Application (TA) loading mechanism allows a privileged attacker to bypass cryptographic checks on TA headers, potentially executing arbitrary code within the TEE or escalating to kernel-level privileges.

MitigationApply vendor-provided patches for the TEE/TrustZone implementation and review TA loading policies to ensure all headers are properly validated against trusted signing keys.

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
Radeon Rx Vega 56 FirmwareOperating system
Affected:all versions
Radeon Rx Vega 64 FirmwareOperating system
Affected:all versions
Ryzen 3 5300ge FirmwareOperating system
Affected:all versions
Ryzen 3 5300g FirmwareOperating system
Affected:all versions
Ryzen 5 5600ge FirmwareOperating system
Affected:all versions

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. Check AMD driver or software version
    On Windows, run 'driverquery /v | findstr -i amd' or check the installed AMD software via Programs and Features. On Linux, check /var/log/kern.log or use 'dmidecode' to find the system model, then cross-reference with the installed AMD driver package version.
    Affected if The installed driver/software version is below 22.10.20 for Enterprise Driver, below 22.q2 for Radeon Pro Software, or below 22.5.2 for Radeon Software.
  2. Check system firmware version for affected Ryzen/Vega hardware
    Run 'dmidecode -t bios' or 'dmidecode -t system' to identify the system model. For graphics cards, use GPU-Z, 'lspci -v', or the AMD Radeon Software to view firmware versions.
    Affected if The system uses a Ryzen 3 5300ge, Ryzen 3 5300g, Ryzen 5 5600ge, Radeon Rx Vega 56, or Radeon Rx Vega 64 with any firmware version.
  3. Verify TEE/TrustZone is enabled
    On AMD systems, check if Secure Memory Encryption (SME) or Platform Security Processor (PSP) is active. On Windows, run 'msinfo32' and look for 'TEE' or 'TrustZone' status. On Linux, check /sys/kernel/debug or use 'dmesg' for TEE-related messages.
    Affected if TEE or TrustZone is present and enabled on the system, making the TA loading mechanism relevant.
  4. Inspect Trusted Application loading configuration
    Review any TEE management tools or logs that show loaded Trusted Applications. Check for custom or test TAs that may have been loaded without proper signature validation.
    Affected if Any custom or third-party TAs are present in the TEE environment, indicating potential exploitation of the signature verification bypass.

You are affected if your system has an AMD component (driver, software, or firmware) matching the affected versions or hardware models listed AND uses TEE/TrustZone functionality where Trusted Applications can be loaded.

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 vendor-provided patches for the TEE/TrustZone implementation and review TA loading policies to ensure all headers are properly validated against trusted signing keys.

Recommended fix Moderate confidence

Enterprise Driver: 22.10.20+ | Radeon Pro Software: 22.q2+ | Radeon Software: 22.5.2+ | Firmware: latest available AMD update

  1. 1. Identify the exact AMD product and component from the affected list (Enterprise Driver, Radeon Pro Software, Radeon Software, or specific firmware)
  2. 2. For Enterprise Driver: Upgrade to version 22.10.20 or later from AMD's official driver download page
  3. 3. For Radeon Pro Software: Upgrade to version 22.q2 or later from AMD's professional graphics driver page
  4. 4. For Radeon Software: Upgrade to version 22.5.2 or later from AMD's consumer driver page
  5. 5. For firmware components (Radeon Rx Vega 56/64, Ryzen 3 5300ge/g, Ryzen 5 5600ge): Check AMD's firmware/BIOS update repository for available updates addressing this vulnerability
  6. 6. After updating, verify the new version is applied by checking system information or driver version

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 / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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