CVE-2021-30293
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 · uneditedPossible assertion due to lack of input validation in PUSCH configuration in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT
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 confidencePossible assertion failure in PUSCH (Physical Uplink Shared Channel) configuration due to lack of input validation in Qualcomm Snapdragon chipset firmware. This is a baseband/modem firmware vulnerability affecting automotive, compute, connectivity, consumer IoT, and industrial IoT devices using affected Snapdragon platforms.
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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/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 Qualcomm modem/baseband firmware componentsCheck device firmware, modem diagnostic logs, or system information for installed Qualcomm firmware modules such as Ar6003, Ar8035, Csrb31024, Fsm10055, Mdm9215, Mdm9607, Mdm9615, or Mdm9628Affected if Any of these firmware components are present in the system
-
Verify PUSCH configuration is activeCheck modem or baseband configuration settings for PUSCH (Physical Uplink Shared Channel) parameters. This may be accessible via modem AT commands, diagnostic interfaces, or vendor-specific configuration toolsAffected if PUSCH configuration is enabled or present in the modem settings
-
Confirm device uses affected Snapdragon platformIdentify the specific Snapdragon or Qualcomm chipset model in the device. Cross-reference with the affected firmware list (Ar6003, Ar8035, Csrb31024, Fsm10055, Mdm9215, Mdm9607, Mdm9615, Mdm9628)Affected if The device contains any of the listed firmware components and operates on a Qualcomm Snapdragon platform
-
Check modem firmware versionQuery the modem firmware version through diagnostic ports, engineering modes, or vendor-specific tools. Since all versions are affected, any version response indicates potential exposureAffected if Modem firmware responds with a version number for any affected component
A device is affected if it contains any of the listed Qualcomm firmware components (Ar6003, Ar8035, Csrb31024, Fsm10055, Mdm9215, Mdm9607, Mdm9615, Mdm9628) and has PUSCH configuration enabled, since all versions of these firmware components 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 vendor-supplied firmware updates from Qualcomm and device manufacturers that address the input validation flaw in PUSCH configuration. Until patches are available, monitor for vendor advisories and restrict exposure to untrusted network inputs where possible.
- Consultation4.0 h
- Implementation8.0 h
- Testing12.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,616.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-30293 — 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-30293 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