CVE-2021-30301
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 denial of service due to out of memory while processing RRC and NAS OTA message in Snapdragon Auto, Snapdragon Industrial IOT, Snapdragon Mobile
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 confidenceA denial of service vulnerability exists in Qualcomm Snapdragon chipsets (Auto, Industrial IOT, Mobile) where processing specially crafted RRC (Radio Resource Control) and NAS (Non-Access Stratum) OTA (Over-The-Air) messages can trigger an out-of-memory condition, causing the device to become unresponsive or crash.
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 the Qualcomm chipset model in your deviceCheck the device hardware specifications, baseband info, or system-on-chip (SoC) details to determine the specific Qualcomm chipset (e.g., Qca6390, Qca6696, Ar8035). On Android, this may appear in Settings > About Phone > Chipset or via 'getprop' commands. On Linux IoT devices, check 'lspci', 'lsusb', or board documentation.Affected if The chipset model matches one of: Ar8035, Qca6390, Qca6391, Qca6574a, Qca6595au, Qca6696, Qca8081, or Qca8337
-
Determine the baseband/modem firmware versionAccess the baseband firmware version through device settings (Settings > About Phone > Baseband version), or via AT commands (e.g., 'AT+CGMR' or 'AT+GMR' on modem interfaces), or through manufacturer firmware documentation.Affected if The firmware version corresponds to any version of the affected chipset models listed above (all versions are affected)
-
Confirm the device processes OTA (Over-The-Air) updatesVerify the device has cellular or wireless communication capability that receives RRC (Radio Resource Control) and NAS (Non-Access Stratum) OTA messages. This is typical for mobile phones, cellular IoT devices, and wireless modems using the affected Qualcomm chipsets.Affected if The device has active cellular/mobile connectivity and receives OTA updates from network carriers (normal operation for affected devices)
Your environment is affected if your device or network infrastructure uses any of the listed Qualcomm chipsets (Ar8035, Qca6390, Qca6391, Qca6574a, Qca6595au, Qca6696, Qca8081, Qca8337) with any firmware version and has cellular/wireless connectivity that processes OTA RRC/NAS messages.
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 firmware updates from device manufacturers that include the Qualcomm fix for this vulnerability. Users should monitor for and install available security patches from their device OEMs or carriers.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-30301 — 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-30301 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