CVE-2021-46759· NVD / CVE Program· CNA AMD

Improper syscall input validation in AMD TEE (Trusted Execution Environment) may allow an attacker with physical access and control of a Uap

Improper syscall input validation in AMD TEE (Trusted Execution Environment) may allow an attacker with physical access and control of a Uapp that runs under the bootloader to reveal the contents of the ASP (AMD Secure Processor) bootloader accessible memory to a serial port, resulting in a potential loss of integrity.

MediumCVSS 6.1 · v3.1—No exploit No fix recorded

Memory safety

Published: May 9, 2023
Updated: Jun 17, 2026
EPSS: 0.3% · 19th percentile
CWE: CWE-787

Follow this CVE

Report tools

JSON

Action score

Monitor

Low priority for now.

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

CISA SSVC decision

Exploitation: none
Automatable: no
Technical impact: total

Vulnrichment: CISA's decision-tree inputs.

Noroxi analysis

No Noroxi analysis for this record yet

We don't hand-write analysis for the hundreds of thousands of vulnerabilities in the database; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.

We use this product, ask for help

Affected systems

Vendor	Product	CPE
amd	ryzen 5300g firmware	cpe:2.3:o:amd:ryzen_5300g_firmware
amd	ryzen 5300g	cpe:2.3:h:amd:ryzen_5300g
amd	ryzen 5300ge firmware	cpe:2.3:o:amd:ryzen_5300ge_firmware
amd	ryzen 5300ge	cpe:2.3:h:amd:ryzen_5300ge
amd	ryzen 5500 firmware	cpe:2.3:o:amd:ryzen_5500_firmware
amd	ryzen 5500	cpe:2.3:h:amd:ryzen_5500
amd	ryzen 5600 firmware	cpe:2.3:o:amd:ryzen_5600_firmware
amd	ryzen 5600	cpe:2.3:h:amd:ryzen_5600
amd	ryzen 5600g firmware	cpe:2.3:o:amd:ryzen_5600g_firmware
amd	ryzen 5600g	cpe:2.3:h:amd:ryzen_5600g
amd	ryzen 5600ge firmware	cpe:2.3:o:amd:ryzen_5600ge_firmware
amd	ryzen 5600ge	cpe:2.3:h:amd:ryzen_5600ge

and 100 more

Affected versions

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

amd athlon gold 3150g firmwarepicassopi-fp5_1.0.0.e
amd athlon gold 3150g firmwarepollockpi-ft5_1.0.0.4
amd athlon gold 3150ge firmwarepicassopi-fp5_1.0.0.e
amd athlon gold 3150ge firmwarepollockpi-ft5_1.0.0.4
amd athlon silver 3050ge firmwarepicassopi-fp5_1.0.0.e
amd athlon silver 3050ge firmwarepollockpi-ft5_1.0.0.4
amd ryzen 1200 (af) firmwarecomboam4pi_1.0.0.9
amd ryzen 1200 (af) firmwarecomboam4v2_pi_1.2.0.8
amd ryzen 1200 (af) firmwarepinnaclepi-am4_1.0.0.d
amd ryzen 1200 (af) firmwareraven-fp5-am4_1.1.0.f
amd ryzen 1600 (af) firmwarecomboam4pi_1.0.0.9
amd ryzen 1600 (af) firmwarecomboam4v2_pi_1.2.0.8
amd ryzen 1600 (af) firmwarepinnaclepi-am4_1.0.0.d
amd ryzen 1600 (af) firmwareraven-fp5-am4_1.1.0.f
amd ryzen 2200g firmwarecomboam4pi_1.0.0.9
amd ryzen 2200g firmwarecomboam4v2_pi_1.2.0.8
amd ryzen 2200g firmwarepinnaclepi-am4_1.0.0.d
amd ryzen 2200g firmwareraven-fp5-am4_1.1.0.f
amd ryzen 2200ge firmwarecomboam4pi_1.0.0.9
amd ryzen 2200ge firmwarecomboam4v2_pi_1.2.0.8

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 Athlon™ 3000 Series Mobile Processors with Radeon™ Graphics “Pollock”
- variousaffected
AMD Athlon™ 3000 Series Mobile Processors with Radeon™ Graphics “Dali”/”Dali” ULP
- variousaffected
AMD Ryzen™ 2000 series Desktop Processors “Raven Ridge” AM4
- variousaffected
AMD Ryzen™ 2000 Series Mobile Processors “Raven Ridge” FP5
- variousaffected
AMD Ryzen™ 3000 Series Mobile processor, 2nd Gen AMD Ryzen™ Mobile Processors with Radeon™ Graphics “Picasso”
- variousaffected
AMD Ryzen™ 3000 Series Mobile Processors with Radeon™ Graphics “Renoir”
- variousaffected
AMD Ryzen™ 5000 Series Desktop processor with Radeon™ Graphics “Cezanne” AM4
- variousaffected
AMD Ryzen™ 5000 Series Mobile processors with Radeon™ Graphics “Cezanne”
- variousaffected
AMD Ryzen™ 5000 Series Mobile Processors with Radeon™ Graphics “Lucienne”
- variousaffected

Same product

amd: all records

Other highest-scoring records for the same primary product.

CVE-2021-46754Insufficient input validation in the ASP (AMD Secure Processor) bootloader may allow an attacker with a compromised Uapp or ABL to coerce th
36Monitor
CVE-2021-46794Insufficient bounds checking in ASP (AMD Secure Processor) may allow for an out of bounds read in SMI (System Management Interface) mailbox
30Monitor
CVE-2021-46749Insufficient bounds checking in ASP (AMD Secure Processor) may allow for an out of bounds read in SMI (System Management Interface) mailbox
30Monitor
CVE-2021-46792Time-of-check Time-of-use (TOCTOU) in the BIOS2PSP command may allow an attacker with a malicious BIOS to create a race condition causing th
23Monitor

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.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

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: high · data can be read
Integrity: high · data or configuration can be modified
Availability: none

Attack vector: Physical
Attack complexity: Low
Privileges required: None
User interaction: None
Scope: Unchanged
Confidentiality impact: High
Integrity impact: High
Availability impact: None

Weakness class (CWE)

CWE-787 · Out-of-bounds Write

CVSS vector

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

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

www.amd.com/en/corporate/product-security/bulletin/AMD-SB-4001

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

All records

Noroxi analysis

No Noroxi analysis for this record yet

We use this product, ask for help

Data sources and verification

CNA: AMD

CVE.org (CNA)Jan 27, 2025, 5:34 PM UTC
CISA ADPJan 27, 2025, 5:34 PM UTC
NVDJun 17, 2026, 12:15 AM UTC
FIRST EPSSSep 29, 2026, 12:00 AM UTC

Each line is when that source was last processed for this record.

You’re seeing every CVE. Add your stack to narrow the list down to the ones that affect you.

Add your stack