dbcve.org
Radeon SoftwareApplication · Amd

CVE-2021-26367

MEDIUM · 6.0 CVSS v3.1 Published 2024-08-13
Fix available
A fix is available. Upgrade to 23.12.1 or later.
See remediation →
62/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
A malicious attacker in x86 can misconfigure the Trusted Memory Regions (TMRs), which may allow the attacker to set an arbitrary address range for the TMR, potentially leading to a loss of integrity and availability.

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 x86 vulnerability allows a malicious attacker to misconfigure Trusted Memory Regions (TMRs), enabling them to set arbitrary address ranges. This can lead to loss of integrity and availability by allowing the attacker to control memory regions that should be restricted.

MitigationApply relevant firmware/microcode updates from CPU vendors and implement proper access controls around TMR configuration in system firmware (BIOS/UEFI).

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:< 23.12.1<= 23.q4
Ryzen 9 5980hx FirmwareOperating system
Affected:< cezannepi-fp6_1.0.0.6
Ryzen 3 3300u FirmwareOperating system
Affected:< picassopi-fp5_1.0.0.e
Ryzen 3 3350u FirmwareOperating system
Affected:< picassopi-fp5_1.0.0.e
Ryzen 5 3450u FirmwareOperating system
Affected:< picassopi-fp5_1.0.0.e
Ryzen 5 3500u FirmwareOperating system
Affected:< picassopi-fp5_1.0.0.e
Ryzen 5 3500c FirmwareOperating system
Affected:< picassopi-fp5_1.0.0.e
Ryzen 5 3550h FirmwareOperating system
Affected:< picassopi-fp5_1.0.0.e

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
High
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:N/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 your AMD Ryzen processor model
    Run 'wmic cpu get name' on Windows or 'cat /proc/cpuinfo' on Linux to see the exact CPU model
    Affected if The CPU is a Ryzen 9 5980hx, Ryzen 3 3300u, Ryzen 3 3350u, Ryzen 5 3450u, Ryzen 5 3500u, Ryzen 5 3500c, or Ryzen 5 3550h
  2. Check the system firmware version
    Enter BIOS/UEFI setup during boot or use 'dmidecode -s bios-version' on Linux or check the BIOS version in Windows System Information (msinfo32)
    Affected if The firmware version is older than cezannepi-fp6_1.0.0.6 (for Ryzen 9 5980hx) or older than picassopi-fp5_1.0.0.e (for all other affected Ryzen models)
  3. Check AMD Radeon Software version if applicable
    Open AMD Radeon Software and click on the gear icon to view the version, or check 'Programs and Features' in Windows for 'AMD Radeon Software'
    Affected if The installed version is less than 23.12.1 or is a 23.q4 release

You are affected if you have one of the listed Ryzen processors with firmware below the specified versions, or if you have AMD Radeon Software versions below 23.12.1 (or 23.q4), as these contain the vulnerable TMR configuration logic.

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 23.12.1 or later
Fixed in 23.12.1
Interim mitigation

Apply relevant firmware/microcode updates from CPU vendors and implement proper access controls around TMR configuration in system firmware (BIOS/UEFI).

Recommended fix High confidence

Radeon Software 23.12.1 or later; Ryzen firmware: cezannepi-fp6_1.0.0.6 for Ryzen 9 5980hx, picassopi-fp5_1.0.0.e for Ryzen 3/5 variants

  1. Check current Radeon Software version by opening AMD Radeon Software and navigating to Settings > About
  2. Download Radeon Software version 23.12.1 or later from the official AMD website at www.amd.com
  3. Install the updated Radeon Software and restart the system when prompted
  4. For affected Ryzen processors, update the system BIOS/UEFI to a version that includes the patched firmware (cezannepi-fp6_1.0.0.6 or picassopi-fp5_1.0.0.e depending on processor model)
  5. Verify the update was successful by checking the firmware version through AMD's firmware update tools or system BIOS information
Caveat Firmware updates may require BIOS/UEFI update which carries some risk; ensure stable power during update process

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

Fix this in Radeon Software Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA3.0 h
27.0 hours of engineering $4,800
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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