dbcve.org
Aqt1000 FirmwareOperating system · Qualcomm

CVE-2021-30350

HIGH · 7.8 CVSS v3.1 Published 2022-06-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
80/100
Remediation priority · High
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
Lack of MBN header size verification against input buffer can lead to memory corruption in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Wearables

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

This is a memory corruption vulnerability in Qualcomm Snapdragon chips caused by missing bounds checking on MBN (Mobile Broadcast Network) header size fields. When processing input buffers, the MBN header size is not verified against the actual buffer size, allowing an attacker to trigger buffer overflows and corrupt memory.

MitigationApply Qualcomm firmware/security updates for affected Snapdragon variants. Users should check with device manufacturers 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
Aqt1000 FirmwareOperating system
Affected:all versions
Ar8035 FirmwareOperating system
Affected:all versions
Csrb31024 FirmwareOperating system
Affected:all versions
Qca6390 FirmwareOperating system
Affected:all versions
Qca6391 FirmwareOperating system
Affected:all versions
Qca6420 FirmwareOperating system
Affected:all versions
Qca6426 FirmwareOperating system
Affected:all versions
Qca6430 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
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/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 the Qualcomm chip model in the device
    On Android devices, run 'getprop ro.qcom.config' or check /proc/cpuinfo for the chip identifier. On other embedded systems, check dmesg for Qualcomm module loading or review boot logs for chip detection messages.
    Affected if The chip model is one of: Aqt1000, Ar8035, Csrb31024, Qca6390, Qca6391, Qca6420, Qca6426, or Qca6430
  2. Verify the chip is a Snapdragon or Qualcomm processor
    Confirm the identified chip is a Qualcomm product. Check device specifications, system information panels, or run 'lspci'/'lsusb' on embedded boards for Qualcomm USB/network adapters.
    Affected if The device contains any of the listed affected Qualcomm firmware products
  3. Determine if MBN (Mobile Broadcast Network) processing is in use
    Check system logs (dmesg, journalctl) for MBN-related messages or examine running services related to broadcast/TV functionality. On mobile devices, check if any broadcast TV or media streaming services are active.
    Affected if The device actively processes MBN-formatted input buffers, which triggers the vulnerable code path in the firmware
  4. Check firmware version if accessible
    Attempt to read firmware version via vendor-specific tools (e.g., 'cat /sys/firmware/devicetree/base/model' for embedded devices, or check AT command responses on modem interfaces). Note: The advisory states all versions are affected.
    Affected if Any firmware version is installed on the affected chip models, as all versions are vulnerable according to the CVE description

A device is affected if it contains any of the listed Qualcomm chip models (Aqt1000, Ar8035, Csrb31024, Qca6390, Qca6391, Qca6420, Qca6426, Qca6430) and uses MBN header processing functionality, since all firmware versions for these chips lack the bounds check on MBN header size fields.

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 Qualcomm firmware/security updates for affected Snapdragon variants. Users should check with device manufacturers for available patches.

Fix this in Aqt1000 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-30350 — 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-30350 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