CVE-2021-30289
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 lack of range check while processing a DIAG command for COEX management in Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music, 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 · moderate confidenceA buffer overflow vulnerability exists in the DIAG command processing for COEX (coexistence) management in Qualcomm Snapdragon chips. The lack of proper range checking when processing the DIAG command allows data to be written beyond allocated buffer boundaries, potentially leading to 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 chipset modelRetrieve the Qualcomm chipset identifier from the device's system information, boot logs, or via AT commands (e.g., AT+QCFG="system"). Common locations: /proc/cpuinfo, boot messages, or modem diagnostic logs.Affected if The chipset model matches any of the following: Apq8009w, Apq8017, Apq8096au, Aqt1000, Csrb31024, Fsm10055, Fsm10056, or Mdm8207.
-
Check the firmware versionQuery the modem firmware version through AT commands (e.g., AT+CGMR, AT+QVER), diagnostic interfaces, or by reading firmware version files from the filesystem if accessible.Affected if Any firmware version is present on an affected chipset, as all versions of the listed products are vulnerable.
-
Verify DIAG diagnostic interface availabilityCheck if the DIAG (Diagnostic) interface is accessible. This can be done by examining device ports (/dev/diag, /dev/ttyUSB*), checking for DIAG-related kernel drivers, or testing with diagnostic tools if the interface is exposed.Affected if The DIAG interface is enabled and accessible on the device, as this is the attack vector for exploiting the buffer overflow.
-
Inspect COEX management configurationReview COEX (coexistence) management settings and logs. Check if COEX functionality is active by examining relevant configuration files, radio coexistence managers, or through AT commands specific to COEX management if available.Affected if COEX management is enabled and the device uses DIAG command processing for COEX operations.
A device is affected if it uses any of the listed Qualcomm chipset models (Apq8009w, Apq8017, Apq8096au, Aqt1000, Csrb31024, Fsm10055, Fsm10056, Mdm8207) with the DIAG interface accessible and COEX management active.
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.
dbcve · scopedApply vendor-supplied firmware updates from Qualcomm to address the missing range check in the DIAG command processing for COEX management. Coordinate with affected device OEMs/ODMs to obtain and deploy patched firmware.
Firmware version containing Qualcomm security patch for CVE-2021-30289 (contact OEM/vendor for exact version)
- Contact the device OEM or hardware vendor to obtain and apply the latest security patch for the affected Qualcomm chipset firmware
- Verify with the vendor that the patch specifically addresses CVE-2021-30289 and includes the range check fix for DIAG command processing in COEX management
- After patching, validate that the COEX management functionality operates correctly and the buffer overflow vulnerability is remediated
- For embedded/IoT devices using these chipsets, ensure firmware update mechanisms are in place and tested
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation8.0 h
- Implementation12.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $9,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-30289 — 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-30289 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