CVE-2021-30288
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 stack overflow due to improper length check of TLV while copying the TLV to a local stack variable in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer Electronics Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon IoT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wired Infrastructure and Networking
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 confidenceA stack overflow vulnerability exists in Qualcomm Snapdragon chipsets due to improper length validation when copying TLV (Type-Length-Value) data to a local stack buffer. The lack of bounds checking before the copy operation allows data exceeding the buffer size to be written, potentially enabling code execution or denial of service.
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
- 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 checksWork through these to decide whether this CVE applies to you.
-
Identify the Qualcomm chipset model in your systemCheck system documentation, device specifications, or use commands like 'lspci', 'lsusb', or check /proc/cpuinfo for ARM-based devices to identify the Qualcomm chipset (Apq8009, Apq8053, Apq8096au, Aqt1000, Ar8031, Ar8035, Csr8811, or Csra6620)Affected if The chipset model matches one of the affected models: Apq8009, Apq8053, Apq8096au, Aqt1000, Ar8031, Ar8035, Csr8811, or Csra6620
-
Locate the firmware version for the Qualcomm chipsetCheck the modem or wireless firmware version through vendor-specific tools, bootloader logs, or system firmware directories (often in /lib/firmware or /etc/firmware). For embedded devices, consult the vendor documentation on accessing chipset firmware version.Affected if The firmware version cannot be determined or is an unpatched release (note: all versions of the listed products are affected according to the advisory)
-
Determine if TLV parsing functionality is activeMonitor network or modem traffic logs for TLV (Type-Length-Value) data processing. This typically occurs in baseband/modem firmware operations related to wireless communications. Check if the chipset's modem or wireless functions are actively processing data.Affected if The chipset is actively processing TLV data through the affected code path in the firmware
You are affected if your device or system incorporates any of the listed Qualcomm chipset models (Apq8009, Apq8053, Apq8096au, Aqt1000, Ar8031, Ar8035, Csr8811, Csra6620) and uses their firmware for TLV data processing, since all firmware versions of these products are vulnerable.
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-supplied firmware updates from Qualcomm for affected Snapdragon product lines. Implement proper length validation before copying TLV data to stack buffers.
- Consultation8.0 h
- Implementation24.0 h
- Testing16.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $15,616.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-30288 — 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-30288 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