dbcve.org
Qcm4290 FirmwareOperating system · Qualcomm

CVE-2020-11130

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'Possible buffer overflow in WIFI hal process due to copying data without checking the buffer length' in Snapdragon Auto, Snapdragon Compute, Snapdragon Industrial IOT, Snapdragon Mobile in QCM4290, QCS4290, QM215, QSM8350, SA6145P, SA6155, SA6155P, SA8155, SA8155P, SC8180X, SC8180XP, SDX55, SDX55M, SM4250, SM4250P, SM6115, SM6115P, SM6125, SM6250, SM6350, SM7125, SM7225, 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

A buffer overflow vulnerability exists in the WiFi Hardware Abstraction Layer (HAL) process where data is copied into a buffer without validating the buffer length first. This memory corruption issue in the WiFi firmware could potentially allow an attacker to execute arbitrary code or cause denial of service via specially crafted wireless packets.

MitigationApply vendor-provided firmware updates for affected Snapdragon chipsets. Since this is a firmware-level vulnerability in the WiFi HAL, workarounds are limited; contact the device manufacturer (OEM) for specific patch availability and update scheduling.

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
Qcm4290 FirmwareOperating system
Affected:all versions
Qcs4290 FirmwareOperating system
Affected:all versions
Qm215 FirmwareOperating system
Affected:all versions
Qsm8350 FirmwareOperating system
Affected:all versions
Sa6145p FirmwareOperating system
Affected:all versions
Sa6155 FirmwareOperating system
Affected:all versions
Sa6155p FirmwareOperating system
Affected:all versions
Sa8155 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 chipset model
    Check the device system information, CPU info, or chipset identification. On Linux systems this may be in /proc/cpuinfo or via 'lscpu'. On Android check Settings > About Phone > Chipset or use 'getprop' commands.
    Affected if The chipset model matches one of the following: Qcm4290, Qcs4290, Qm215, Qsm8350, Sa6145p, Sa6155, Sa6155p, or Sa8155
  2. Locate WiFi firmware version
    Query the WiFi driver or firmware subsystem for version information. On Linux this may be accessible via 'iw' or 'wiphy' information, or check firmware files in /lib/firmware/qca or similar vendor-specific paths. On Android use 'dmesg' or WiFi diagnostic tools.
    Affected if A WiFi firmware version is reported and the chipset from step 1 is one of the affected models
  3. Verify WiFi is enabled
    Check if the WiFi interface is active or powered on. Use 'ip link show' or 'iw dev' on Linux, or check WiFi status in system settings on Android.
    Affected if WiFi is currently enabled or was recently enabled on the device
  4. Confirm all versions affected
    Since the vendor advisory states all versions of the listed firmware are affected, compare your identified chipset and firmware version against the affected product list.
    Affected if The device uses any of the affected chipset models (Qcm4290, Qcs4290, Qm215, Qsm8350, Sa6145p, Sa6155, Sa6155p, Sa8155) regardless of firmware version

The device is affected if it contains any of the listed Qualcomm chipsets and has WiFi functionality enabled, since all firmware versions for these models are vulnerable.

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 vendor-provided firmware updates for affected Snapdragon chipsets. Since this is a firmware-level vulnerability in the WiFi HAL, workarounds are limited; contact the device manufacturer (OEM) for specific patch availability and update scheduling.

Fix this in Qcm4290 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,120
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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