dbcve.org
Ryzen 7 5700g FirmwareOperating system · Amd

CVE-2023-20559

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 AmdCpmGpioInitSmm may allow a privileged attacker to tamper with the SMM handler potentially leading to 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 · high confidence

This is a firmware vulnerability in AMD processors affecting the AmdCpmGpioInitSMM handler in the Platform Security Processor (PSP) firmware. Insufficient control flow management allows a privileged attacker to tamper with SMM (System Management Mode) handlers, potentially achieving code execution at the highest privilege level and escalating privileges.

MitigationApply the AMD-provided firmware/BIOS update that addresses CVE-2023-20559. Organizations should check with their hardware vendors for available firmware updates and follow standard firmware deployment procedures.

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 the AMD processor model
    Run system information commands such as 'wmic cpu get name' on Windows or 'lscpu | grep Model name' on Linux. Alternatively, check the system information or BIOS setup screen.
    Affected if The processor is an AMD Ryzen 7 5700g, 5700ge, Ryzen 5 5600g, 5600ge, Ryzen 3 5300g, 5300ge, Ryzen 9 5980hx, or Ryzen 9 5980hs.
  2. Check the BIOS/firmware version
    Retrieve the BIOS version using 'wmic bios get smbiosbiosversion' on Windows, 'dmidecode -s bios-version' on Linux, or by viewing the BIOS/UEFI setup screen during boot.
    Affected if The installed BIOS version cannot be determined or is below the fixed versions.
  3. Compare version against affected ranges for AM4 platform
    For Ryzen 5000G series desktop processors (5700g, 5700ge, 5600g, 5600ge, 5300g, 5300ge), compare your BIOS version to comboam4_v2_pi_1.2.0.6c. Note the version format used by your system (which may differ from the AMD version string).
    Affected if The BIOS version is earlier than comboam4_v2_pi_1.2.0.6c for these processors.
  4. Compare version against affected ranges for FP6 platform
    For Ryzen 9 5980hx and 5980hs mobile processors, compare your BIOS version to cezannepi-fp6_1.0.0.9. Note the version format used by your system.
    Affected if The BIOS version is earlier than cezannepi-fp6_1.0.0.9 for these processors.
  5. Verify PSP firmware version if accessible
    Some systems may expose PSP (Platform Security Processor) firmware version through specialized tools such as AMD's PSPFWInfo or through UEFI shell tools. Consult vendor documentation for your specific system.
    Affected if The PSP firmware version cannot be verified or is not available through standard system tools.

A system is affected if it uses one of the listed AMD Ryzen processors and its BIOS/PSP firmware version is below the fixed version for its specific processor family (comboam4_v2_pi_1.2.0.6c for 5000G series or cezannepi-fp6_1.0.0.9 for Ryzen 9 5980hx/hs).

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 AMD-provided firmware/BIOS update that addresses CVE-2023-20559. Organizations should check with their hardware vendors for available firmware updates and follow standard firmware deployment procedures.

Recommended fix High confidence

AMD Ryzen 5000 G-Series Desktop Processors: comboam4_v2_pi_1.2.0.6c | AMD Ryzen 9 5980hx/5980hs Mobile Processors: cezannepi-fp6_1.0.0.9

  1. 1. Identify the exact AMD Ryzen processor model (e.g., Ryzen 7 5700g, Ryzen 9 5980hx) from the affected product list.
  2. 2. Visit the official AMD support website (www.amd.com) and navigate to the drivers and support section for your specific processor model.
  3. 3. Download the latest BIOS/firmware update: For AM4 socket processors (Ryzen 7 5700g/5700ge, Ryzen 5 5600g/5600ge, Ryzen 3 5300g/5300ge), download version comboam4_v2_pi_1.2.0.6c or later. For FP6 mobile processors (Ryzen 9 5980hx, Ryzen 9 5980hs), download version cezannepi-fp6_1.0.0.9 or later.
  4. 4. Apply the firmware update by following AMD's flashing instructions, typically through the BIOS/UEFI update utility or AMD's Ryzen Master software.
  5. 5. After updating, verify the firmware version has been successfully applied by checking the system BIOS information.
Caveat Firmware updates carry inherent risk; ensure stable power during BIOS flashing to avoid rendering the system unbootable

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

Fix this in Ryzen 7 5700g Firmware Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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