dbcve.org
Enterprise DriverApplication · Amd

CVE-2021-26393

MEDIUM · 5.5 CVSS v3.1 Published 2022-11-09
Fix available
A fix is available. Upgrade to 22.q2 / 22.5.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
Insufficient memory cleanup in the AMD Secure Processor (ASP) Trusted Execution Environment (TEE) may allow an authenticated attacker with privileges to generate a valid signed TA and potentially poison the contents of the process memory with attacker controlled data resulting in a loss of confidentiality.

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

This vulnerability exists in AMD Secure Processor's Trusted Execution Environment (TEE) where insufficient memory cleanup during Trusted Application (TA) processing allows an authenticated attacker with appropriate privileges to generate a valid signed TA and inject attacker-controlled data into process memory, resulting in confidentiality loss.

MitigationApply AMD-provided firmware updates for the Secure Processor; verify that only trusted and signed applications are loaded into the TEE and review access controls for TA signing capabilities.

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 2200ge FirmwareOperating system
Affected:all versions
Ryzen 3 2200g FirmwareOperating system
Affected:all versions
Ryzen 5 2400ge 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
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. Identify AMD Secure Processor presence
    Check system information for AMD processor with Platform Security Processor (PSP) or AMD Secure Processor. On Linux, this may appear in /proc/cpuinfo or via 'dmidecode'. On Windows, check System Information or use 'wmic baseboard get product,manufacturer'
    Affected if System uses an AMD processor with Secure Processor/TEE enabled ( Ryzen 2000 series and Vega GPUs are listed as affected)
  2. Determine AMD Enterprise Driver version
    On Windows, open Programs and Features and look for 'AMD Enterprise Driver' or use 'wmic product get name,version'. On Linux, check via 'lsmod' for amd_sp or check /var/log for amd driver logs
    Affected if AMD Enterprise Driver version is found to be less than 22.10.20 (or version cannot be determined)
  3. Determine AMD Radeon Software version
    Open AMD Radeon Software (Radeon Settings) and check About section, or on Windows check 'Add or Remove Programs' for 'AMD Radeon Software' version. On Linux check 'amdgpu-install' --list or 'rocminfo' output
    Affected if AMD Radeon Software version is less than 22.5.2 or version cannot be determined
  4. Determine AMD Radeon Pro Software version
    On Windows, check 'Add or Remove Programs' or Program Files for 'AMD Radeon Pro' software version. Check the specific Pro driver version installed
    Affected if AMD Radeon Pro Software version is less than 22.q2 (or quarterly version prior to Q2 2022)
  5. Check firmware version for affected GPU models
    For AMD Radeon Rx Vega 56 or Vega 64, use GPU-Z, AMD Radeon Software (under Hardware > GPU Settings > BIOS), or 'rocm-smi' (Linux) to read the GPU firmware/BIOS version. For Ryzen 2200G/2400GE, use 'dmidecode' -t bios or AMD Ryzen Master utility
    Affected if GPU model is Radeon Rx Vega 56 or Vega 64 (any firmware version), or CPU is Ryzen 3 2200G/2200GE/5 2400GE (any firmware version) - all listed firmware versions are affected

The environment is likely affected if it uses any of the listed AMD processors/GPUs with the Secure Processor TEE enabled AND the driver/firmware versions are below the specified thresholds, or if using the fully-affected Vega or Ryzen 2000 series firmware variants.

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 updates for the Secure Processor; verify that only trusted and signed applications are loaded into the TEE and review access controls for TA signing capabilities.

Recommended fix Moderate confidence

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

  1. For Enterprise Driver users: Upgrade to version 22.10.20 or later from AMD's official driver download page
  2. For Radeon Pro Software users: Upgrade to version 22.q2 or later from AMD's professional graphics support site
  3. For Radeon Software users: Upgrade to version 22.5.2 or later from AMD's consumer graphics driver page
  4. After upgrading, verify the new driver/firmware version is installed via Device Manager or AMD Radeon Software settings

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-26393 — 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-26393 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