dbcve.org
Apq8009w FirmwareOperating system · Qualcomm

CVE-2020-11175

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'Use after free issue in Bluetooth transport driver when a method in the object is accessed after the object has been deleted due to improper timer handling.' in Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Wearables in APQ8009W, MSM8909W, QCS605, QM215, SA6155, SA6155P, SA8155, SA8155P, SDA640, SDA670, SDA855, SDM1000, SDM640, SDM670, SDM710, SDM845, SDX50M, SDX55, SDX55M, SM6125, SM6350, SM7225, SM7250, SM7250P, SM8150, SM8150P, SM8250, SXR1120, SXR1130, 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 · high confidence

A use-after-free vulnerability exists in the Bluetooth transport driver where improper timer handling allows a method to be accessed on an object after it has been deleted. This memory safety issue could allow an attacker to execute arbitrary code or cause a denial of service by exploiting the dangling pointer.

MitigationApply vendor-supplied firmware patches from Qualcomm for affected Snapdragon chipsets. Until patches are available, minimize exposure by disabling Bluetooth when not in use and monitoring for anomalous device 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 data
Apq8009w FirmwareOperating system
Affected:all versions
Msm8909w FirmwareOperating system
Affected:all versions
Qcs605 FirmwareOperating system
Affected:all versions
Qm215 FirmwareOperating system
Affected:all versions
Sa6155 FirmwareOperating system
Affected:all versions
Sa6155p FirmwareOperating system
Affected:all versions
Sa8155 FirmwareOperating system
Affected:all versions
Sa8155p 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
    Determine the specific Snapdragon/Qualcomm chipset model installed in the device (check system information, device specs, or /proc/cpuinfo on Android devices)
    Affected if The chipset matches any of: Apq8009w, Msm8909w, Qcs605, Qm215, Sa6155, Sa6155p, Sa8155, or Sa8155p
  2. Confirm firmware version is present
    Retrieve the firmware version string for the identified Qualcomm chipset (check via device settings, manufacturer documentation, or firmware version command)
    Affected if A firmware version is returned (all versions of listed chipsets are affected)
  3. Verify Bluetooth is enabled
    Check whether the Bluetooth radio is powered on or active on the device (via system settings, Bluetooth status API, or bluetoothctl show on Linux)
    Affected if Bluetooth is currently enabled or was recently enabled on the device
  4. Check Bluetooth driver status
    Inspect the loaded Bluetooth transport driver modules or status (lsmod on Android/Linux embedded devices, or check driver info via dmesg)
    Affected if The Bluetooth transport driver is loaded and the timer handling component is in use

The device is affected if it uses any of the listed Qualcomm chipsets (Apq8009w, Msm8909w, Qcs605, Qm215, Sa6155, Sa6155p, Sa8155, Sa8155p) with Bluetooth enabled, since all firmware versions of these chipsets contain the use-after-free vulnerability in the Bluetooth transport driver.

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-supplied firmware patches from Qualcomm for affected Snapdragon chipsets. Until patches are available, minimize exposure by disabling Bluetooth when not in use and monitoring for anomalous device behavior.

Fix this in Apq8009w Firmware Scoped from the published advisory
  • Consultation6.0 h
  • Implementation20.0 h
  • Testing16.0 h
  • Review / QA8.0 h
50.0 hours of engineering $8,640
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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