dbcve.org
Ryzen 3 3100 FirmwareOperating system · Amd

CVE-2021-26346

MEDIUM · 5.5 CVSS v3.1 Published 2023-01-11
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
57/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
Failure to validate the integer operand in ASP (AMD Secure Processor) bootloader may allow an attacker to introduce an integer overflow in the L2 directory table in SPI flash resulting in a potential denial of service.

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 validation failure in the AMD Secure Processor (ASP) bootloader allows an attacker to trigger an integer overflow in the L2 directory table within SPI flash memory, potentially causing denial of service.

MitigationApply the AMD firmware update for the Secure Processor bootloader to address the integer validation flaw; verify no regression in secure boot functionality after update.

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 3 3100 FirmwareOperating system
Affected:all versions
Ryzen 3 3200g FirmwareOperating system
Affected:all versions
Ryzen 3 3200u FirmwareOperating system
Affected:all versions
Ryzen 3 3250c FirmwareOperating system
Affected:all versions
Ryzen 3 3250u FirmwareOperating system
Affected:all versions
Ryzen 3 3300g FirmwareOperating system
Affected:all versions
Ryzen 3 3300u FirmwareOperating system
Affected:all versions
Ryzen 3 3300x FirmwareOperating system
Affected:all versions

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
None
Integrity
None
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/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 processor model
    Run 'wmic cpu get name' or check system documentation to confirm the exact CPU model number
    Affected if The CPU is NOT one of: Ryzen 3 3100, 3200g, 3200u, 3250c, 3250u, 3300g, 3300u, or 3300x - if your model is not in this list, you are likely not affected by this specific CVE
  2. Locate AMD Secure Processor firmware version
    Use AMD's firmware tools or check system BIOS/UEFI under 'Security' or 'AMD CBS' settings for 'AMD Secure Processor' information; some systems show this in Windows Device Manager under 'System devices' as 'AMD Secure Processor'
    Affected if You cannot determine the firmware version because the AMD Secure Processor is not visible or accessible on your system - the vulnerability may still exist but cannot be verified without ASP access
  3. Verify AMD Secure Processor is enabled
    Enter BIOS/UEFI setup and look for 'AMD Secure Processor', 'PSP' (Platform Security Processor), or 'fTPM' settings under Security or Advanced menus; confirm it shows as enabled
    Affected if The AMD Secure Processor is disabled in BIOS - the specific vulnerability in the ASP bootloader would not be exploitable in this configuration
  4. Check SPI flash memory configuration
    This requires low-level hardware or diagnostic tools that can read the SPI flash; on some systems, tools like 'flashrom' or AMD's diagnostics can inspect the L2 directory table structure if you have proper permissions
    Affected if You lack the technical capability or hardware access to inspect SPI flash contents - the vulnerability exists in the bootloader code stored in SPI flash memory but cannot be verified through simple software checks

You are affected if you use one of the listed Ryzen 3 processors (3100, 3200g, 3200u, 3250c, 3250u, 3300g, 3300u, 3300x) with the AMD Secure Processor enabled and cannot confirm your ASP bootloader firmware has been updated to address the integer overflow in the L2 directory table validation.

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

Apply the AMD firmware update for the Secure Processor bootloader to address the integer validation flaw; verify no regression in secure boot functionality after update.

Fix this in Ryzen 3 3100 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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