dbcve.org
Qsm8350 FirmwareOperating system · Qualcomm

CVE-2020-3632

HIGH · 7.8 CVSS v3.1 Published 2020-11-12
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
u'Incorrect validation of ring context fetched from host memory can lead to memory overflow' in Snapdragon Compute, Snapdragon Mobile in QSM8350, SC7180, SDX55, SDX55M, SM6150, SM6250, SM6250P, SM7125, SM7150, SM7150P, SM7250, SM7250P, SM8150, SM8150P, SM8250, SM8350, SM8350P, SXR2130, SXR2130P

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 confidence

This is a memory validation vulnerability in Qualcomm Snapdragon chipsets where incorrect validation of ring context data fetched from host memory can lead to memory overflow (buffer overflow). The vulnerability stems from missing or improper bounds checking when processing ring context structures, potentially allowing an attacker to trigger memory corruption and potentially achieve code execution in a privileged context.

MitigationApply the firmware update provided by Qualcomm through the device OEM. Users should check for and install available system updates for affected devices. Organizations with Snapdragon-connected IoT or mobile device fleets should inventory affected hardware and coordinate with OEM vendors for patch deployment.

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
Qsm8350 FirmwareOperating system
Affected:all versions
Sc7180 FirmwareOperating system
Affected:all versions
Sdx55 FirmwareOperating system
Affected:all versions
Sdx55m FirmwareOperating system
Affected:all versions
Sm6150 FirmwareOperating system
Affected:all versions
Sm6250 FirmwareOperating system
Affected:all versions
Sm6250p FirmwareOperating system
Affected:all versions
Sm7125 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 chipset model
    On Android devices, check Settings > About Phone > Model or use 'getprop ro.product.board' command. For IoT devices, consult hardware documentation or use 'lspci' or 'lsusb' to identify the Snapdragon chipset.
    Affected if The chipset model matches any of: Qsm8350, Sc7180, Sdx55, Sdx55m, Sm6150, Sm6250, Sm6250p, or Sm7125
  2. Check the baseband firmware version
    On Android devices, go to Settings > About Phone > Baseband version or dial *#*#4636#*#* and select Phone information. The baseband version is typically displayed as a string like 'MPSS.HE.2.0.2-xxxxxx'.
    Affected if The device uses one of the affected chipsets listed above (all firmware versions are vulnerable)
  3. Verify kernel ring buffer for related errors
    Check dmesg or kernel logs for any memory corruption or ring buffer errors related to the modem or DSP components using 'dmesg | grep -i ring' or 'dmesg | grep -i mss'
    Affected if Errors appear related to ring context processing in the baseband subsystem
  4. Check modem subsystem crash logs
    Review /sys/kernel/debug/msm_subsys or use 'logcat -b crash' to look for modem subsystem restarts or memory corruption indications
    Affected if Frequent modem subsystem crashes or memory corruption errors are present
  5. Inventory Snapdragon-connected IoT devices
    For IoT deployments, use network discovery or SNMP to identify device firmware versions. Consult vendor documentation to confirm the chipset model used.
    Affected if Any device is found running firmware on the affected chipset models

The environment is affected if any device uses a Qualcomm Snapdragon chipset from the affected list (Qsm8350, Sc7180, Sdx55, Sdx55m, Sm6150, Sm6250, Sm6250p, Sm7125), as all firmware versions for these chipsets contain the vulnerability.

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 the firmware update provided by Qualcomm through the device OEM. Users should check for and install available system updates for affected devices. Organizations with Snapdragon-connected IoT or mobile device fleets should inventory affected hardware and coordinate with OEM vendors for patch deployment.

Fix this in Qsm8350 Firmware Scoped from the published advisory
  • Consultation8.0 h
  • Testing16.0 h
  • Review / QA8.0 h
32.0 hours of engineering $5,440
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,704.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2020-3632 — 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-2020-3632 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