dbcve.org
Ryzen 3945wx FirmwareOperating system · Amd

CVE-2021-46760

CRITICAL · 9.8 CVSS v3.1 Published 2023-05-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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 or compromised UApp or ABL can send a malformed system call to the bootloader, which may result in an out-of-bounds memory access that may potentially lead to an attacker leaking sensitive information or achieving code execution.

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

A malformed system call sent from a compromised or malicious UApp or ABL to the bootloader triggers an out-of-bounds memory access vulnerability, potentially allowing attackers to leak sensitive information or achieve arbitrary code execution due to insufficient bounds checking in the bootloader's system call handler.

MitigationImplement rigorous input validation and bounds checking in the bootloader's system call handler to prevent out-of-bounds memory accesses; consider adding integrity verification for calling applications and employing secure boot mechanisms to ensure only trusted code can interact with the bootloader.

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 3945wx FirmwareOperating system
Affected:= castlepeakwspi-swrx8_1.0.0.9= chagallwspi-swrx8_1.0.0.2= castlepeakpi-sp3r3_1.0.0.7
Ryzen 3955wx FirmwareOperating system
Affected:= castlepeakwspi-swrx8_1.0.0.9= chagallwspi-swrx8_1.0.0.2= castlepeakpi-sp3r3_1.0.0.7
Ryzen 3960x FirmwareOperating system
Affected:= castlepeakwspi-swrx8_1.0.0.9= chagallwspi-swrx8_1.0.0.2= castlepeakpi-sp3r3_1.0.0.7
Ryzen 3970x FirmwareOperating system
Affected:= castlepeakwspi-swrx8_1.0.0.9= chagallwspi-swrx8_1.0.0.2= castlepeakpi-sp3r3_1.0.0.7
Ryzen 3975wx FirmwareOperating system
Affected:= castlepeakwspi-swrx8_1.0.0.9= chagallwspi-swrx8_1.0.0.2= castlepeakpi-sp3r3_1.0.0.7
Ryzen 3990x FirmwareOperating system
Affected:= castlepeakwspi-swrx8_1.0.0.9= chagallwspi-swrx8_1.0.0.2= castlepeakpi-sp3r3_1.0.0.7
Ryzen 3995wx FirmwareOperating system
Affected:= castlepeakwspi-swrx8_1.0.0.9= chagallwspi-swrx8_1.0.0.2= castlepeakpi-sp3r3_1.0.0.7

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

CVSS:3.1/AV:N/AC:L/PR:N/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 processor model
    Run 'wmic cpu get Name,ProcessorId,Description' on Windows or 'lscpu | grep -E "Model name|CPU(s)"' on Linux to confirm the CPU is an AMD Ryzen 3945wx, 3955wx, 3960x, 3970x, 3975wx, 3990x, or 3995wx.
    Affected if The processor is one of the listed AMD Ryzen models (3945wx, 3955wx, 3960x, 3970x, 3975wx, 3990x, or 3995wx).
  2. Retrieve the system firmware version
    On Windows, run 'wmic bios get SMBIOSBIOSVersion' or check the BIOS/UEFI version in the system information. On Linux, run 'dmidecode -s bios-version' or check /sys/class/dmi/id/bios_version.
    Affected if The firmware version matches castlepeakwspi-swrx8_1.0.0.9, chagallwspi-swrx8_1.0.0.2, or castlepeakpi-sp3r3_1.0.0.7.
  3. Check the PSP/TSM firmware component version
    Use AMD's PSP/TPM tools or platform-specific tools provided by the OEM (such as AMD Ryzen Master or OEM firmware update utilities) to query the PSP bootloader version. This often requires administrator or root privileges.
    Affected if The PSP bootloader component version corresponds to the affected firmware versions listed above.
  4. Verify if untrusted UApp/ABL code execution is possible
    Review system hardening and application whitelisting policies. Check if the system allows loading and executing unsigned or untrusted userspace applications that could interact with the bootloader interface.
    Affected if The environment permits execution of untrusted or unsigned applications that could send system calls to the bootloader.
  5. Check Secure Boot status
    On Windows, run 'bcdedit /enum all' and look for 'secure boot' status. On Linux, run 'mokutil --sb-state' to check if Secure Boot is enabled.
    Affected if Secure Boot is disabled, as this reduces protection against malicious UApp/ABL code interacting with the bootloader.

A user is affected if they are running one of the specified AMD Ryzen processors with a matching firmware version (castlepeakwspi-swrx8_1.0.0.9, chagallwspi-swrx8_1.0.0.2, or castlepeakpi-sp3r3_1.0.0.7) and have the ability for untrusted applications to send system calls to the bootloader.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement rigorous input validation and bounds checking in the bootloader's system call handler to prevent out-of-bounds memory accesses; consider adding integrity verification for calling applications and employing secure boot mechanisms to ensure only trusted code can interact with the bootloader.

Fix this in Ryzen 3945wx Firmware Scoped from the published advisory
  • Consultation6.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
34.0 hours of engineering $6,000
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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