CVE-2021-30310
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 buffer overflow due to Improper validation of received CF-ACK and CF-Poll data frames in Snapdragon Auto, Snapdragon Connectivity, Snapdragon Consumer Electronics Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon IoT, Snapdragon Mobile, Snapdragon Voice & Music
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 confidenceBuffer overflow vulnerability in Qualcomm Snapdragon chipsets stemming from improper validation of CF-ACK and CF-Poll data frames in the baseband/firmware layer, potentially allowing remote code execution or denial of service via malformed network frames.
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 modelCheck the device specifications, system information, or baseband processor details to determine the exact Snapdragon or Qualcomm chipset variant (e.g., Apq8009, Apq8017, Apq8053, Apq8096au, Csrb31024, Mdm9206, Mdm9250, Mdm9607)Affected if The chipset matches one of the affected models: Apq8009, Apq8017, Apq8053, Apq8096au, Csrb31024, Mdm9206, Mdm9250, or Mdm9607
-
Determine the baseband firmware versionQuery the baseband firmware version through device diagnostic tools, AT commands (e.g., AT+CGMR), or system firmware information. Compare the installed version against the affected product listingAffected if The firmware is from a product listed as affected (all versions of the specified products are affected)
-
Verify baseband network processing is enabledCheck the baseband processor configuration to confirm that the network stack is active and capable of processing wireless data frames, including CF-ACK and CF-Poll frame types used in certain wireless protocolsAffected if The baseband firmware is actively processing network frames and the CF-ACK/CF-Poll handling feature is present in the firmware configuration
A device is affected if it uses any of the listed Qualcomm chipset models (Apq8009, Apq8017, Apq8053, Apq8096au, Csrb31024, Mdm9206, Mdm9250, Mdm9607) with baseband firmware that processes CF-ACK and CF-Poll data frames.
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 Qualcomm-provided firmware/microcode updates for affected Snapdragon components; contact original equipment manufacturers for platform-specific security patches.
- Consultation4.0 h
- Implementation8.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,192.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-30310 — 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-30310 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