Skip to content
Noroxi
NVD / CVE Program· CNA AMD

CVE-2021-46758: Insufficient validation of SPI flash addresses in the ASP (AMD Secure Processor) bootloader may allow an attacker to read data in memory map

Noroxi assessment

Priority: Monitor (action score 24/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.32% (FIRST EPSS).
  • Physical access to the device is required. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
  • According to the record, no fixed version is available yet.

Low priority for now. Update when a fix is released; follow the vendor's advisory.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

Insufficient validation of SPI flash addresses in the ASP (AMD Secure Processor) bootloader may allow an attacker to read data in memory mapped beyond SPI flash resulting in a potential loss of availability and integrity.

MediumCVSS 6.1 · v3.1—No exploit No fix recorded
Published
Nov 14, 2023
Updated
Jun 17, 2026
EPSS
0.3% · 25th percentile
CWE
—

Report tools

JSON

Action score

24

Monitor

Low priority for now.

CVSS
24 / 40 · 6.1 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.3%

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • No fixed version yet

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2021-46758

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for amd records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
amdryzen 7 5700g firmware
amdryzen 7 5700g
amdryzen 7 5700ge firmware
amdryzen 7 5700ge
amdryzen 5 5600g firmware
amdryzen 5 5600g
amdryzen 5 5600ge firmware
amdryzen 5 5600ge
amdryzen 3 5300g firmware
amdryzen 3 5300g
amdryzen 3 5300ge firmware
amdryzen 3 5300ge

and 110 more

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • amd ryzen 3 4300u firmwarebefore renoirpi-fp6_1.0.0.a
  • amd ryzen 3 5125c firmwarebefore cezannepi-fp6_1.0.0.c
  • amd ryzen 3 5300g firmwarebefore comboam4v2_pi_1.2.0.8
  • amd ryzen 3 5300ge firmwarebefore comboam4v2_pi_1.2.0.8
  • amd ryzen 3 5300u firmwarebefore cezannepi-fp6_1.0.0.c
  • amd ryzen 3 5400u firmwarebefore cezannepi-fp6_1.0.0.c
  • amd ryzen 3 5425u firmwarebefore cezannepi-fp6_1.0.0.c
  • amd ryzen 3 7335u firmwarebefore rembrandtpi-fp7_1.0.0.5
  • amd ryzen 3 pro 7330u firmwarebefore cezannepi-fp6_1.0.0.c
  • amd ryzen 5 4500u firmwarebefore renoirpi-fp6_1.0.0.a
  • amd ryzen 5 4600h firmwarebefore renoirpi-fp6_1.0.0.a
  • amd ryzen 5 4600hs firmwarebefore renoirpi-fp6_1.0.0.a
  • amd ryzen 5 4600u firmwarebefore renoirpi-fp6_1.0.0.a
  • amd ryzen 5 4680u firmwarebefore renoirpi-fp6_1.0.0.a
  • amd ryzen 5 5500h firmwarebefore cezannepi-fp6_1.0.0.c
  • amd ryzen 5 5500u firmwarebefore cezannepi-fp6_1.0.0.c
  • amd ryzen 5 5560u firmwarebefore cezannepi-fp6_1.0.0.c
  • amd ryzen 5 5600g firmwarebefore comboam4v2_pi_1.2.0.8
  • amd ryzen 5 5600ge firmwarebefore comboam4v2_pi_1.2.0.8
  • amd ryzen 5 5600h firmwarebefore cezannepi-fp6_1.0.0.c

Versions reported by the vendor

Affected version ranges reported by the assigning authority (AMD). Independent of NVD's CPE analysis and usually ahead of it.

  • AMD AMD Ryzen™ 5000 Series Processors with Radeon™ Graphics “Barcelo”

    • variousaffected

  • AMD AMD Ryzen™ 6000 Series Processors with Radeon™ Graphics "Rembrandt"

    • variousaffected

  • AMD AMD Ryzen™ 7030 Series Mobile Processors with Radeon™ Graphics “Barcelo-R”

    • variousaffected

  • AMD AMD Ryzen™ 7035 Series Processors with Radeon™ Graphics “Rembrandt-R”

    • variousaffected

  • AMD Ryzen™ 4000 Series Mobile Processors with Radeon™ Graphics “Renoir” FP6

    • variousaffected

  • AMD Ryzen™ 5000 Series Desktop Processor with Radeon™ Graphics “Cezanne”

    • variousaffected

  • AMD Ryzen™ 5000 Series Mobile Processors with Radeon™ Graphics “Cezanne”

    • variousaffected

  • AMD Ryzen™ 5000 Series Mobile Processors with Radeon™ Graphics “Lucienne”

    • variousaffected

  • AMD Ryzen™ 7000 Series Desktop Processors “Raphael” XD3

    • variousaffected

Same product

amd: all records

Other highest-scoring records for the same primary product.

  • CVE-2023-20596Improper input validation in the SMM Supervisor may allow an attacker with a compromised SMI handler to gain Ring0 access potentially leadin
    39Monitor
  • CVE-2023-20559 Insufficient control flow management in AmdCpmGpioInitSmm may allow a privileged attacker to tamper with the SMM handler potentially lead
    35Monitor
  • CVE-2023-20558 Insufficient control flow management in AmdCpmOemSmm may allow a privileged attacker to tamper with the SMM handler potentially leading to
    35Monitor

Published before and after this one in the same product

  • ← EarlierCVE-2021-26382Jul 14, 2022 · An attacker with root account privileges can load any legitimately signed firmware image into the Audio Co-Processor (ACP,) irrespective of
    17Monitor
  • ← EarlierCVE-2021-26384Jul 14, 2022 · A malformed SMI (System Management Interface) command may allow an attacker to establish a corrupted SMI Trigger Info data structure, potent
    31Monitor
  • Later →CVE-2023-20579Feb 13, 2024 · Improper Access Control in the AMD SPI protection feature may allow a user with Ring0 (kernel mode) privileged access to bypass protections
    24Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

No fix version is recorded for this entry. Check the references for vendor advisories.

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Physical access to the device is required.
  • No account or password is required.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
none
Integrity
high · data or configuration can be modified
Availability
high · the service can be disrupted
Attack vector
Physical
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality impact
None
Integrity impact
High
Availability impact
High

Weakness class (CWE)

—

CVSS vector

CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.

References

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records