CVE-2021-1952
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 over read occurs due to lack of length check of request buffer in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Voice & Music
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 over-read vulnerability exists in multiple Qualcomm Snapdragon chip products due to insufficient length validation of request buffers. The lack of proper bounds checking allows an attacker to read memory beyond the allocated buffer boundary, potentially exposing sensitive information or causing system instability.
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 Qualcomm Snapdragon components in the systemReview system/device information outputs such as 'lspci', 'lsusb', 'dmidecode', 'cat /proc/cpuinfo', or device firmware tables (UEFI/ACPI) to enumerate present Qualcomm hardware modulesAffected if Any of the following firmware modules are present: Aqt1000, Ar8031, Ar8035, Csra6620, Csra6640, Mdm9150, Mdm9205, or Qca4004
-
Check firmware version of identified Qualcomm componentsQuery the firmware version through vendor-specific tools, device APIs, or by reading firmware version strings from /sys or device firmware dumpsAffected if The firmware version matches any of the affected product names (all versions of these firmware products are vulnerable)
-
Verify the vulnerable wireless or audio module is activeCheck if the relevant network (Ar8031/Ar8035/Qca4004), modem (Mdm9150/Mdm9205), or audio (Csra6620/Csra6640) interface or service is enumerated and enabled in the operating system (e.g., check ifconfig, ip link, or associated driver status)Affected if The module is present and actively enumerated by the operating system
-
Confirm the request buffer handling code path is reachableDetermine whether the firmware component processes external input buffers through its request handler interface - this typically requires access to firmware debugging, vendor documentation, or security advisory details about the specific attack surfaceAffected if The component accepts and processes request buffers from untrusted sources
A system is affected if it contains any of the listed Qualcomm firmware components (Aqt1000, Ar8031, Ar8035, Csra6620, Csra6640, Mdm9150, Mdm9205, Qca4004) and the vulnerable buffer processing code path is reachable, since all versions of these products lack proper length validation.
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/microcode updates from Qualcomm and subsequent device manufacturer updates to address the missing length validation in affected Snapdragon components.
- Consultation8.0 h
- Implementation4.0 h
- Testing12.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,320.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-1952 — 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-1952 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