CVE-2021-46792: Time-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
Noroxi assessment
Priority: Monitor (action score 23/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.39% (FIRST EPSS).
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. Special conditions such as timing or configuration are required.
- 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
Time-of-check Time-of-use (TOCTOU) in the BIOS2PSP command may allow an attacker with a malicious BIOS to create a race condition causing the ASP bootloader to perform out-of-bounds SRAM reads upon an S3 resume event potentially leading to a denial of service.
- Published
- May 9, 2023
- Updated
- Jun 17, 2026
- EPSS
- 0.3% · 33th percentile
- CWE
- CWE-367
Report tools
Action score
23
Monitor
Low priority for now.
- CVSS
- 23 / 40 · 5.9 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.3%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
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.
Running WordPress? Scan your site free with WP Lens
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 helpAffected 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.
| 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 98 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.4
- amd athlon gold 3150ge firmwarepicassopi-fp5_1.0.0.4
- amd athlon silver 3050ge firmwarepicassopi-fp5_1.0.0.4
- amd ryzen 1200 (af) firmwarepinnaclepi-am4_1.0.0.7
- amd ryzen 1200 (af) firmwareraven-fp5-am4_1.0.0.9
- amd ryzen 1600 (af) firmwarepinnaclepi-am4_1.0.0.7
- amd ryzen 1600 (af) firmwareraven-fp5-am4_1.0.0.9
- amd ryzen 2200g firmwarepinnaclepi-am4_1.0.0.7
- amd ryzen 2200g firmwareraven-fp5-am4_1.0.0.9
- amd ryzen 2200ge firmwarepinnaclepi-am4_1.0.0.7
- amd ryzen 2200ge firmwareraven-fp5-am4_1.0.0.9
- amd ryzen 2300x firmwarepinnaclepi-am4_1.0.0.7
- amd ryzen 2300x firmwareraven-fp5-am4_1.0.0.9
- amd ryzen 2400g firmwarepinnaclepi-am4_1.0.0.7
- amd ryzen 2400g firmwareraven-fp5-am4_1.0.0.9
- amd ryzen 2400ge firmwarepinnaclepi-am4_1.0.0.7
- amd ryzen 2400ge firmwareraven-fp5-am4_1.0.0.9
- amd ryzen 2500x firmwarepinnaclepi-am4_1.0.0.7
- amd ryzen 2500x firmwareraven-fp5-am4_1.0.0.9
- amd ryzen 2600 firmwarepinnaclepi-am4_1.0.0.7
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 “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 recordsOther 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 th36Monitor
- 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
Published before and after this one in the same product
- ← EarlierCVE-2021-46759May 9, 2023 · Improper syscall input validation in AMD TEE
(Trusted Execution Environment) may allow an attacker with physical access and
control of a Uap24Monitor
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.
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 researchersFinders, 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
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- Special conditions such as timing or configuration are required.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- High
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-367 · Time-of-check Time-of-use (TOCTOU) Race ConditionCVSS vector
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/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.
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.