CVE-2021-26392
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 · uneditedInsufficient verification of missing size check in 'LoadModule' may lead to an out-of-bounds write potentially allowing an attacker with privileges to gain code execution of the OS/kernel by loading a malicious TA.
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 · high confidenceInsufficient verification of a missing size check in the LoadModule function leads to an out-of-bounds write vulnerability. An attacker with appropriate privileges can exploit this by loading a malicious Trusted Application (TA), potentially achieving OS/kernel-level code execution. The vulnerability stems from the LoadModule not properly validating size parameters before memory operations.
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< 22.10.20< 22.q2< 22.5.2all 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 installed AMD Enterprise Driver versionCheck the installed version of Amd Enterprise Driver on the system. On Windows, this can typically be found in Device Manager under the driver properties, or via system information tools. On Linux, check /proc/driver/ or use amdgpu driver version information.Affected if The version is lower than 22.10.20, indicating it is affected by the vulnerability.
-
Identify installed AMD Radeon Software versionCheck the installed AMD Radeon Software version. On Windows, this is usually visible in the Radeon Software UI under 'System' or 'About'. On Linux, check the amdgpu driver version through system utilities.Affected if The version is lower than 22.5.2, indicating it contains the vulnerable LoadModule function.
-
Identify AMD Radeon Pro Software versionCheck the installed AMD Radeon Pro Software version. This is typically found in the software's system information or about section.Affected if The version is lower than 22.q2, indicating the size validation flaw is present.
-
Check for vulnerable firmware on Ryzen 3 2200G/2200GECheck the firmware version of AMD Ryzen 3 2200G or 2200GE processors if present in the system. This can be verified through BIOS/UEFI information or system firmware reporting tools.Affected if The system uses a Ryzen 3 2200G or 2200GE processor with any firmware version, as all versions are affected.
-
Check for vulnerable firmware on Ryzen 5 2400GECheck the firmware version of AMD Ryzen 5 2400GE processor if present in the system. Verify through BIOS/UEFI or firmware reporting tools.Affected if The system uses a Ryzen 5 2400GE processor with any firmware version, as all versions are affected.
-
Check for vulnerable firmware on Radeon RX Vega 56/64Identify if the system contains an AMD Radeon RX Vega 56 or RX Vega 64 GPU and check its firmware version through GPU information utilities or system hardware listing.Affected if The system has a Radeon RX Vega 56 or RX Vega 64 GPU with any firmware version, as all versions contain the vulnerability.
The system is affected if it runs any of the affected AMD software with version below the specified thresholds, or contains any of the specific CPU/GPU models with firmware versions as listed, since the LoadModule function lacks proper size validation for Trusted Applications.
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 · scoped22.q222.5.222.10.20
Apply vendor-provided security patches that implement proper size validation in the LoadModule function. Additionally, ensure that only signed and verified Trusted Applications from trusted sources are loaded into the secure execution environment.
Enterprise Driver 22.10.20+, Radeon Pro Software 22.q2+, Radeon Software 22.5.2+
- Identify the specific AMD product in use (Enterprise Driver, Radeon Pro Software, Radeon Software, or relevant firmware)
- For AMD Enterprise Driver users: Upgrade to version 22.10.20 or later
- For Radeon Pro Software users: Upgrade to version 22.q2 or later
- For Radeon Software users: Upgrade to version 22.5.2 or later
- For firmware on Radeon Rx Vega 56/64, Ryzen 3 2200g/ge, Ryzen 5 2400ge: Check for BIOS/driver updates that include updated firmware; apply all available AMD AGESA and firmware updates
- Verify the installation by checking the driver/software version after upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing5.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-26392 — 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-26392 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