CVE-2021-1938
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 assertion due to improper verification while creating and deleting the peer in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer Electronics Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial 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 · moderate confidenceVulnerability in Qualcomm Snapdragon chipsets where improper verification during peer creation and deletion operations can lead to an assertion failure. This affects multiple product lines including Mobile, Auto, Compute, Connectivity, Consumer IOT, Industrial IOT, Voice & Music, and Wired Infrastructure. The high CVSS indicates potential for denial of service or unexpected system behavior.
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
- 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 checksWork through these to decide whether this CVE applies to you.
-
Identify the Qualcomm chipset model in your deviceCheck device specifications, system information, or hardware diagnostics to determine the exact Snapdragon chipset model (e.g., via 'lspci', 'lsusb', device manager, or vendor documentation)Affected if The chipset model matches one of the affected models: Aqt1000, Ar8031, Ar8035, Ar9380, Csr8811, Csra6620, Csra6640, or Csrb31024
-
Locate the firmware version for the identified chipsetAccess the device's firmware information through vendor utilities, boot logs, /proc filesystem, or firmware dumping tools specific to the chipset (methods vary by device type and manufacturer)Affected if The firmware version falls within the affected range for the identified chipset model
-
Check if wireless or connectivity peer management features are activeMonitor system logs, network interface statistics, or debugging interfaces for peer creation and deletion operations in the wireless/connectivity subsystemAffected if Peer creation and deletion operations are being performed by the chipset firmware (the vulnerable code path is exercised)
-
Verify the chipset product line falls within affected categoriesCross-reference the chipset's intended use (Mobile, Auto, Compute, Connectivity, Consumer IOT, Industrial IOT, Voice & Music, or Wired Infrastructure) against the known affected product linesAffected if The device uses a Snapdragon chipset from one of the listed product lines with the vulnerable firmware
You are affected if your device contains any of the specific Qualcomm chipset models (Aqt1000, Ar8031, Ar8035, Ar9380, Csr8811, Csra6620, Csra6640, Csrb31024) running firmware where peer creation/deletion operations are exercised.
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-provided firmware patches from Qualcomm and downstream device manufacturers. As this is a firmware-level issue in Snapdragon chipsets, users should update their devices when OEM patches become available.
- Consultation4.0 h
- Implementation2.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,160.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-1938 — 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-1938 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