dbcve.org
Ar8035 FirmwareOperating system · Qualcomm

CVE-2021-30287

HIGH · 7.5 CVSS v3.1 Published 2022-01-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
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 assertion due to improper validation of symbols configured for PDCCH monitoring in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, 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 confidence

This vulnerability exists in Qualcomm Snapdragon chipsets (Auto, Compute, Connectivity, Industrial IOT, Mobile) where improper validation of symbols configured for PDCCH (Physical Downlink Control Channel) monitoring can trigger an assertion failure. PDCCH is used in LTE/5G networks for control information transmission, and this validation flaw could allow malformed configuration to cause a denial of service via device crash or assertion.

MitigationApply vendor-supplied firmware/security updates from Qualcomm and device manufacturers. Organizations should inventory affected Snapdragon devices and monitor for available patches.

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
Ar8035 FirmwareOperating system
Affected:all versions
Qca6390 FirmwareOperating system
Affected:all versions
Qca6391 FirmwareOperating system
Affected:all versions
Qca6426 FirmwareOperating system
Affected:all versions
Qca6436 FirmwareOperating system
Affected:all versions
Qca6574a FirmwareOperating system
Affected:all versions
Qca6574au FirmwareOperating system
Affected:all versions
Qca6595au 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
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 checks

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

  1. Identify Qualcomm chipset model in your environment
    Review hardware inventory, device specifications, or use commands like 'lspci', 'lshw', or vendor-specific tools to list installed wireless/cellular chipsets. Check product datasheets or modem firmware outputs for the chipset identifier.
    Affected if The chipset matches one of: Ar8035, Qca6390, Qca6391, Qca6426, Qca6436, Qca6574a, Qca6574au, or Qca6595au.
  2. Check firmware version of the affected chipset
    Use vendor-provided tools or AT commands (for cellular modems) such as 'AT+GMR' or firmware version queries to retrieve the current installed firmware version on the chipset.
    Affected if The firmware version is any version (all versions of these chipsets are affected per the advisory).
  3. Verify cellular/LTE/5G connectivity is enabled
    Check if the device has cellular network interfaces active or configured. Look for network interfaces like 'wwan0', 'rmnet0', or similar, and confirm the cellular radio is powered on.
    Affected if The device uses LTE or 5G connectivity, as PDCCH is the Physical Downlink Control Channel used in these networks.
  4. Review system and kernel logs for PDCCH-related assertion failures
    Examine logs in /var/log/, dmesg output, or vendor-specific crash logs for messages containing 'PDCCH', 'assertion', 'assert failed', or sudden modem crashes/restarts.
    Affected if Logs show assertion failures or crashes related to PDCCH configuration or validation.

You are affected if your environment contains any of the listed Qualcomm chipset models (Ar8035, Qca6390, Qca6391, Qca6426, Qca6436, Qca6574a, Qca6574au, Qca6595au) with cellular connectivity enabled, as all firmware versions of these chipsets are vulnerable.

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/security updates from Qualcomm and device manufacturers. Organizations should inventory affected Snapdragon devices and monitor for available patches.

Fix this in Ar8035 Firmware Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing24.0 h
  • Review / QA8.0 h
56.0 hours of engineering $9,520
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2021-30287 — 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-30287 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