CVE-2021-26352
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 bound checks in System Management Unit (SMU) PCIe Hot Plug table may result in access/updates from/to invalid address space that could result in 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 confidenceInsufficient bounds checking in the System Management Unit's (SMU) PCIe Hot Plug table allows access to invalid memory addresses. This can be triggered when the SMU processes hot plug events for PCIe devices, potentially causing the system to read or write to out-of-bounds memory locations, leading to a denial of service condition.
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
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/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 your CPU modelRun 'wmic cpu get name' on Windows or 'cat /proc/cpuinfo' on Linux to confirm the processor modelAffected if The CPU model is one of: Ryzen 5 2600, Ryzen 5 2600x, Ryzen 5 2700, Ryzen 5 2700x, Ryzen 5 3600, Ryzen 5 3600x, Ryzen 7 3700x, or Ryzen 7 3800x
-
Determine SMU firmware versionUse a hardware monitoring tool such as HWiNFO, CPU-Z, or your motherboard vendor's utility to read the System Management Unit firmware versionAffected if Any SMU firmware version is reported on one of the affected CPU models (all versions are affected)
-
Check if PCIe hot plug is enabledAccess the BIOS/UEFI settings during boot and navigate to PCIe or hot plug configuration options, or use 'lspci' with 'hpmctl' on Linux or Device Manager on Windows to inspect hot plug statusAffected if PCIe hot plug support is enabled or the system has hot-pluggable PCIe slots in use
-
Verify BIOS/UEFI firmware versionCheck your BIOS/UEFI version through 'dmidecode -s bios-version' on Linux or the BIOS setup screen on boot, then compare to any vendor advisoriesAffected if The BIOS version is dated before the vendor patch release for this CVE
You are affected if your system uses one of the listed Ryzen CPU models with PCIe hot plug functionality enabled, regardless of SMU firmware version since all versions are vulnerable.
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 vendor-provided SMU/BIOS firmware update that addresses the insufficient bounds checking in the PCIe Hot Plug table handling code. Check with your hardware vendor for available firmware updates.
- Consultation2.0 h
- Implementation1.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-26352 — 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-26352 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