dbcve.org
Qca2062 FirmwareOperating system · Qualcomm

CVE-2021-30304

CRITICAL · 9.1 CVSS v3.1 Published 2021-10-20
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
Possible buffer out of bound read can occur due to improper validation of TBTT count and length while parsing the beacon response in Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer Electronics Connectivity

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 · high confidence

A buffer out-of-bounds read vulnerability exists in Qualcomm Snapdragon wireless firmware due to improper validation of the TBTT (Target Beacon Transmission Time) count and length fields when parsing beacon responses. An attacker within wireless range could exploit this by sending a malformed beacon response with excessive TBTT entries or oversized length values, causing the device to read beyond buffer boundaries. At CVSS 9.1, this remote proximity vulnerability can lead to information disclosure or potentially remote code execution.

MitigationApply vendor-supplied firmware patches from Qualcomm and device manufacturers; until patches are available, limit exposure by restricting wireless access to trusted networks and trusted personnel only.

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 data
Qca2062 FirmwareOperating system
Affected:all versions
Qca2064 FirmwareOperating system
Affected:all versions
Qca2065 FirmwareOperating system
Affected:all versions
Qca2066 FirmwareOperating system
Affected:all versions
Sc8280xp FirmwareOperating system
Affected:all versions
Wcd9380 FirmwareOperating system
Affected:all versions
Wcd9385 FirmwareOperating system
Affected:all versions
Wcn6850 FirmwareOperating system
Affected:all versions

CVSS 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
High
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify Qualcomm wireless chipset model
    On Linux, run 'lspci | grep -i network' or 'lshw -C network' to list wireless network devices. On Android, check under Settings > About Phone > SIM Status or use 'dumpsys' commands. On embedded systems, check '/proc/bus/usb/devices' or device tree entries.
    Affected if The chipset matches any of these models: Qca2062, Qca2064, Qca2065, Qca2066, Sc8280xp, Wcd9380, Wcd9385, or Wcn6850
  2. Check wireless firmware version
    On Linux, use 'ethtool -i <interface>' or 'iw list' to retrieve firmware version information. On Android, use 'getprop' commands or manufacturer diagnostic tools. On systems with 'rfkill', check 'rfkill list all'.
    Affected if The reported firmware version is any version (the CVE lists all versions as affected) and the chipset is one of the eight affected models
  3. Verify wireless interface is active
    Run 'ip link show' or 'iwconfig' to confirm the wireless interface exists and is in an UP or UNKNOWN state. Check 'iw dev <interface> info' for operational status.
    Affected if The wireless interface is active and using an affected Qualcomm chipset (the vulnerability is triggered by processing beacon responses, so an active wireless interface is required for exploitation)
  4. Confirm TBTT processing is enabled
    TBTT (Target Beacon Transmission Time) handling is a standard function of 802.11 (Wi-Fi) beacon processing. No specific configuration flag controls this; it is inherent to any device operating as a station (STA) or access point (AP) that processes beacon frames.
    Affected if The device operates in any Wi-Fi mode that processes beacon frames (client mode, AP mode, or monitor mode)

A system is affected if it contains any of the eight listed Qualcomm wireless chipsets (Qca2062, Qca2064, Qca2065, Qca2066, Sc8280xp, Wcd9380, Wcd9385, Wcn6850) and has an active wireless interface, since all firmware versions for these chipsets are vulnerable to CVE-2021-30304.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor-supplied firmware patches from Qualcomm and device manufacturers; until patches are available, limit exposure by restricting wireless access to trusted networks and trusted personnel only.

Fix this in Qca2062 Firmware Scoped from the published advisory
  • Consultation8.0 h
  • Implementation4.0 h
  • Testing16.0 h
  • Review / QA8.0 h
36.0 hours of engineering $6,160
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $9,856.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2021-30304 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2021-30304 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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