dbcve.org
Ryzen 7 5700g FirmwareOperating system · Amd

CVE-2023-20558

HIGH · 8.8 CVSS v3.1 Published 2023-04-02
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable 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 control flow management in AmdCpmOemSmm may allow a privileged attacker to tamper with the SMM handler potentially leading to an escalation of privileges.

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 is a firmware vulnerability in AMD processors affecting the AmdCpmOemSmm component in System Management Mode (SMM). The vulnerability stems from insufficient control flow management, allowing a privileged attacker to tamper with the SMM handler and escalate privileges to the highest level in the system.

MitigationApply BIOS/UEFI firmware updates provided by AMD and motherboard vendors. This requires updating the system firmware to the latest version that addresses this SMM vulnerability.

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

CVSS:3.1/AV:N/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 CPU model
    Run 'wmic cpu get name' or check system information to confirm the AMD Ryzen processor model
    Affected if CPU is NOT 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
  2. Check BIOS/firmware version on AM4 platform CPUs
    Enter BIOS setup or use 'wmic bios get smbiosbiosversion' command; look for firmware version string containing comboam4_v2_pi
    Affected if CPU is Ryzen 3/5/7 5x00g/ge and firmware version is less than 1.2.0.6c OR the version string does not contain 1.2.0.6c or higher
  3. Check BIOS/firmware version on FP6 platform CPUs
    Enter BIOS setup or use 'wmic bios get smbiosbiosversion' command; look for firmware version string containing cezannepi-fp6
    Affected if CPU is Ryzen 9 5980hx/5980hs and firmware version is less than 1.0.0.9 OR the version string does not contain cezannepi-fp6_1.0.0.9 or higher
  4. Confirm SMM configuration status
    Check BIOS/UEFI settings for any SMM lock or protection settings; inspect 'SmmLock' variable via UEFI shell or tool like RWEverything if accessible
    Affected if SMM protection features are disabled or not present, making the tampered handler attack feasible

User is affected if they have one of the listed AMD Ryzen CPUs with firmware version below the specified threshold for their platform (AM4 or FP6).

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 BIOS/UEFI firmware updates provided by AMD and motherboard vendors. This requires updating the system firmware to the latest version that addresses this SMM vulnerability.

Recommended fix High confidence

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

  1. 1. Identify your current BIOS/firmware version by checking the system BIOS setup or using a system information tool.
  2. 2. Download the latest BIOS/firmware update from the official AMD support page for your specific processor model (e.g., Ryzen 7 5700g, Ryzen 9 5980hx).
  3. 3. Ensure the system is connected to a stable power source before initiating the BIOS update process.
  4. 4. Follow AMD's provided instructions to flash the new BIOS, which may involve using a USB drive or the AMD BIOS update utility.
  5. 5. Verify the BIOS has been successfully updated to version comboam4_v2_pi_1.2.0.6c (for AM4 platform: Ryzen 7 5700g, 5700ge, 5 5600g, 5600ge, 3 5300g, 5300ge) or cezannepi-fp6_1.0.0.9 (for FP6 platform: Ryzen 9 5980hx, 5980hs).
Caveat BIOS updates carry inherent risk of system failure if interrupted; ensure stable power and follow update instructions precisely

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
  • Implementation2.0 h
  • Testing6.0 h
  • Review / QA3.0 h
15.0 hours of engineering $2,600
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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