CVE-2021-30276
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 · uneditedImproper access control while doing XPU re-configuration dynamically can lead to unauthorized access to a secure resource in Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Wired Infrastructure and Networking
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 confidenceImproper access control during dynamic XPU re-configuration in Qualcomm Snapdragon chipsets allows unauthorized access to secure resources. This vulnerability stems from insufficient validation during the re-configuration process, potentially enabling a local attacker to bypass security boundaries and access protected assets.
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 if your device uses affected Qualcomm firmware componentsInventory your networked devices and embedded systems to determine if they contain any of the following Qualcomm chipset families: Ar8035, Qca6390, Qca6391, Qca6426, Qca6436, Qca8337, Qca9984, or Qcm2290. Check device specifications, hardware documentation, or network scans for chipset identifiers.Affected if Your environment contains any device using one of the listed Qualcomm firmware components
-
Check the firmware version of affected Qualcomm componentsAccess the device management interface, CLI, or firmware dump to retrieve the installed firmware version for the specific Qualcomm component. Compare against the vendor disclosure which states all versions are affected.Affected if Any version of the listed firmware is installed (all versions are vulnerable)
-
Determine if XPU re-configuration is accessibleReview device configuration and access controls to determine if dynamic XPU (secure processing unit) re-configuration features are exposed or accessible. Check for debug interfaces, diagnostic ports, or management APIs that trigger re-configuration.Affected if Dynamic XPU re-configuration is exposed or accessible without proper authorization controls
-
Verify if the device OEM has applied the Qualcomm fixContact the device OEM or check release notes/changelogs for your specific device model to confirm whether the firmware includes the CVE-2021-30276 patch from Qualcomm.Affected if The device firmware does not include the vendor-specific patch for this CVE
Your environment is affected if you have any devices running the listed Qualcomm firmware components (Ar8035, Qca6390, Qca6391, Qca6426, Qca6436, Qca8337, Qca9984, Qcm2290) without the OEM-specific patch applied.
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 firmware updates provided by the device OEM that include the Qualcomm fix for CVE-2021-30276. Organizations should identify all affected Snapdragon-based devices in their environment and coordinate with vendors for patch deployment.
- Consultation8.0 h
- Implementation4.0 h
- Testing12.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,320.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-30276 — 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-30276 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