dbcve.org
Ryzen 7 5700g FirmwareOperating system · Amd

CVE-2021-26384

HIGH · 7.8 CVSS v3.1 Published 2022-07-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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
A malformed SMI (System Management Interface) command may allow an attacker to establish a corrupted SMI Trigger Info data structure, potentially leading to out-of-bounds memory reads and writes when triggering an SMI resulting in a potential loss of resources.

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 · high confidence

A vulnerability in AMD's System Management Interface (SMI) allows malformed SMI commands to corrupt the SMI Trigger Info data structure, leading to out-of-bounds memory reads and writes during SMI handling. This is a firmware-level memory corruption issue that could allow an attacker to read or write to arbitrary memory locations.

MitigationApply the vendor-provided BIOS/UEFI firmware update that addresses this vulnerability; until then, limit physical access to affected systems and monitor for suspicious system management activity.

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
Ryzen 7 5700g FirmwareOperating system
Affected:< comboam4_v2_pi_1.2.0.6c
Ryzen 7 5700ge FirmwareOperating system
Affected:< comboam4_v2_pi_1.2.0.6c
Ryzen 5 5600g FirmwareOperating system
Affected:< comboam4_v2_pi_1.2.0.6c
Ryzen 5 5600ge FirmwareOperating system
Affected:< comboam4_v2_pi_1.2.0.6c
Ryzen 3 5300g FirmwareOperating system
Affected:< comboam4_v2_pi_1.2.0.6c
Ryzen 3 5300ge FirmwareOperating system
Affected:< comboam4_v2_pi_1.2.0.6c
Ryzen 9 5980hx FirmwareOperating system
Affected:< cezannepi-fp6_1.0.0.9
Ryzen 9 5980hs FirmwareOperating system
Affected:< cezannepi-fp6_1.0.0.9

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 Ryzen processor model
    Run 'wmic cpu get name' or check system information to confirm the processor is one of: Ryzen 7 5700g, Ryzen 7 5700ge, Ryzen 5 5600g, Ryzen 5 5600ge, Ryzen 3 5300g, Ryzen 3 5300ge, Ryzen 9 5980hx, or Ryzen 9 5980hs
    Affected if The processor model matches any of the listed affected Ryzen models
  2. Check the BIOS/UEFI firmware version on AM4 platform
    Access the BIOS/UEFI setup during boot or use 'wmic bios get smbiosbiosversion' from Windows or 'dmidecode -s bios-version' from Linux to retrieve the firmware version
    Affected if The firmware version is earlier than comboam4_v2_pi_1.2.0.6c for Ryzen 5000g/gx series processors
  3. Check the BIOS/UEFI firmware version on FP6 platform
    Access the BIOS/UEFI setup during boot or use 'wmic bios get smbiosbiosversion' from Windows or 'dmidecode -s bios-version' from Linux to retrieve the firmware version
    Affected if The firmware version is earlier than cezannepi-fp6_1.0.0.9 for Ryzen 9 5980hx/hs processors
  4. Verify the platform form factor
    Check the system board or product specifications to determine if the system uses the AM4 socket (desktop APU) or FP6 mobile socket
    Affected if The system uses an affected processor on either the AM4 or FP6 platform and the firmware has not been updated

A system is affected if it contains an AMD Ryzen 5000g-series or Ryzen 9 5980hx/hs processor and its BIOS/UEFI firmware version is lower than the specified fixed versions (comboam4_v2_pi_1.2.0.6c or cezannepi-fp6_1.0.0.9).

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the vendor-provided BIOS/UEFI firmware update that addresses this vulnerability; until then, limit physical access to affected systems and monitor for suspicious system management activity.

Recommended fix High confidence

comboam4_v2_pi_1.2.0.6c for AM4 processors (Ryzen 5000G series) or cezannepi-fp6_1.0.0.9 for FP6 processors (Ryzen 9 5980hx/hs)

  1. Identify your exact AMD Ryzen processor model and determine if it uses AM4 socket (5700g, 5700ge, 5600g, 5600ge, 5300g, 5300ge) or FP6 (5980hx, 5980hs)
  2. Check your current BIOS/firmware version via system BIOS setup or using tools like CPU-Z or inxi
  3. Download the latest BIOS/firmware from the official AMD website (support.amd.com) specific to your motherboard manufacturer or the AMD generic firmware if available
  4. Follow the motherboard manufacturer's instructions to update the BIOS - typically requires creating a USB flash drive with the firmware file and using the BIOS flashback feature or standard BIOS update utility
  5. After updating, verify the firmware version has been changed to comboam4_v2_pi_1.2.0.6c (for AM4) or cezannepi-fp6_1.0.0.9 (for FP6) or later
Caveat Firmware updates carry a risk of system instability if interrupted; ensure stable power during update; some older features may be deprecated in newer BIOS versions

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

Fix this in Ryzen 7 5700g Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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