CVE-2021-26361
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 · uneditedA malicious or compromised User Application (UApp) or AGESA Boot Loader (ABL) could be used by an attacker to exfiltrate arbitrary memory from the ASP stage 2 bootloader potentially leading to information disclosure.
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 confidenceThis AMD vulnerability allows a malicious or compromised User Application (UApp) or AGESA Boot Loader (ABL) to exfiltrate arbitrary memory from the ASP (Application Security Processor) stage 2 bootloader, leading to information disclosure of sensitive data in boot-time memory.
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 dataall versionsall versionsall versionsall versionsall versionsall versionsall versionsall versionsCVSS 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
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
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 your AMD system modelRun 'wmic computersystem get model' or check system BIOS information to determine if the machine uses an affected AMD processor (Ryzen 3 2200u, 2300u, 5125c, 5400u, or Athlon 3050ge, 3150ge, 3150g)Affected if The system model contains any of the affected processor IDs listed in the CVE
-
Check AMD firmware versionAccess UEFI/BIOS settings during boot or use 'dmidecode -s bios-version' to retrieve the current firmware versionAffected if The firmware version is present (all versions of these processors are affected)
-
Verify Secure Boot statusRun 'bcdedit /enum all' and look for 'secureboot' status, or use 'mokutil --sb-state' on LinuxAffected if Secure Boot is disabled or not properly configured - this indicates the mitigation is not in place
-
Check for signed AGESA componentsInspect UEFI/BIOS settings for any 'Authenticated BIOS' or 'BIOS Rollback Protection' settings, and verify boot logs for any unsigned or untrusted AGESA Boot Loader warningsAffected if Unsigned AGESA components are detected or authentication warnings appear in boot logs
You are affected if your system uses any of the listed AMD Ryzen 3 or Athlon processors and Secure Boot is not enabled or trusted AGESA components cannot be verified.
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.
From vendor dataApply AMD-provided firmware updates and ensure only trusted/signed User Applications and AGESA Boot Loader components are executed; verify Secure Boot mechanisms are properly enabled.
- Consultation8.0 h
- Implementation24.0 h
- Testing16.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $15,616.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-26361 — 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-26361 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