CVE-2021-46792
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 · uneditedTime-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.
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 confidenceA TOCTOU race condition exists in the BIOS2PSP command where a malicious BIOS can exploit timing between security check and use during S3 resume, causing the ASP bootloader to perform out-of-bounds SRAM reads leading to potential denial of service.
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= cezannepi-fp6_1.0.0.6= cezannepi-fp6_1.0.0.6= cezannepi-fp6_1.0.0.6= cezannepi-fp6_1.0.0.6= cezannepi-fp6_1.0.0.6= cezannepi-fp6_1.0.0.6= cezannepi-fp6_1.0.0.6= cezannepi-fp6_1.0.0.6CVSS 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
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:H/PR:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify the processor modelRun 'dmidecode -s processor-version' or check system information to determine the exact AMD Ryzen CPU modelAffected if The processor is one of: Ryzen 5300g, 5300ge, 5500, 5600, 5600g, 5600ge, 5600x, or 5700g
-
Verify S3 resume is enabledCheck the system's power management settings via 'powercfg -a' or BIOS setup to see if S3 (sleep) state is available and configuredAffected if S3 resume is enabled and used on the system; the vulnerability triggers during S3 resume transitions
A system is affected if it uses an AMD Ryzen processor from the listed models with firmware version cezannepi-fp6_1.0.0.6 and has S3 resume functionality enabled, as the race condition in the BIOS2PSP command occurs specifically during S3 resume.
Generated from the published advisory. Verify against your own configuration.
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.
dbcve · scopedEnsure BIOS integrity through secure boot mechanisms and signed BIOS updates; apply any vendor-supplied firmware patches for the BIOS2PSP command when available.
AMD AGESA firmware update containing fix for CVE-2021-46792
- Check AMD's support website (www.amd.com) or your motherboard manufacturer's website for the latest BIOS/firmware update for your specific Ryzen processor
- Locate the BIOS update that addresses CVE-2021-46792 or the TOCTOU vulnerability in BIOS2PSP command
- Update the system BIOS to the latest version provided by AMD or your motherboard manufacturer
- After BIOS update, verify the firmware version has been updated from cezannepi-fp6_1.0.0.6
- Test S3 resume functionality to confirm the vulnerability has been addressed
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation8.0 h
- Implementation40.0 h
- Testing24.0 h
- Review / QA16.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $24,448.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-46792 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2021-46792 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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