CVE-2021-26369
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 UApp or ABL may be used by an attacker to send a malformed system call to the bootloader, resulting in out-of-bounds memory accesses.
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 is a bootloader vulnerability in AMD systems (affecting ABL - AMD Boot Loader) where a malicious or compromised user application (UApp) can send malformed system calls to the bootloader, triggering out-of-bounds memory accesses. The attacker needs code execution capability within a UApp to exploit this flaw.
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
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/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 your AMD processor modelRun 'wmic cpu get name' on Windows or 'cat /proc/cpuinfo' on Linux to list the installed AMD CPUAffected if The processor model matches one of these: Amd Athlon 3050ge, Amd Athlon 3150g, Amd Athlon 3150ge, Amd Ryzen 3 2200u, Amd Ryzen 3 2300u, Amd Ryzen 3 3100, Amd Ryzen 3 3300g, or Amd Radeon Software is present
-
Check system manufacturer and BIOS versionRun 'wmic bios get version,manufacturer' on Windows or 'dmidecode -s bios-version' on Linux to retrieve the firmware versionAffected if The system uses one of the affected AMD processors and the BIOS has not been updated to a patched version (contact AMD for patched firmware)
-
Verify if user application (UApp) execution is possibleCheck if the system environment allows loading and executing custom user applications that can issue system calls to the AMD Boot Loader (this is typically a development or specialized embedded feature)Affected if UApp code execution capability exists on the system, which is required to trigger the malformed system calls that cause the out-of-bounds memory access
Your environment is affected if you are running any of the listed AMD processors (Athlon 3050ge, 3150g, 3150ge, Ryzen 3 2200u, 2300u, 3100, 3300g) or Amd Radeon Software, regardless of version, and you have the ability to execute custom user applications that can interface with the bootloader.
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 the AMD-provided firmware/BIOS update that patches the bootloader to include proper bounds checking on system call parameters. Organizations should identify affected AMD hardware and deploy the vendor firmware update through their standard BIOS update processes.
- Consultation12.0 h
- Implementation8.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 $12,288.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-26369 — 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-26369 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