dbcve.org
Apq8009 FirmwareOperating system · Qualcomm

CVE-2019-10517

HIGH · 7.8 CVSS v3.1 Published 2019-12-18
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
Memory is being freed up twice when two concurrent threads are executing in parallel in Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon IoT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables in APQ8009, APQ8017, APQ8053, APQ8096, APQ8096AU, APQ8098, MDM9206, MDM9207C, MDM9607, MDM9650, MSM8909, MSM8909W, MSM8917, MSM8920, MSM8937, MSM8939, MSM8940, MSM8996AU, QCS405, QCS605, SDA660, SDA845, SDM630, SDM636, SDM660, SDM845, SDX20, SM6150, SM7150, SM8150, SM8250, SXR1130, SXR2130

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 double-free vulnerability exists in the memory management of affected Snapdragon chipsets where two concurrent threads can trigger the same memory block to be freed twice, leading to memory corruption and potential code execution. This race condition occurs in the lower-level firmware components handling thread synchronization.

MitigationApply vendor-provided firmware patches from Qualcomm and device manufacturers. This is a firmware-level issue requiring OTA updates from OEM/device vendors rather than application-level remediation.

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
Apq8009 FirmwareOperating system
Affected:all versions
Apq8017 FirmwareOperating system
Affected:all versions
Apq8053 FirmwareOperating system
Affected:all versions
Apq8096 FirmwareOperating system
Affected:all versions
Apq8096au FirmwareOperating system
Affected:all versions
Apq8098 FirmwareOperating system
Affected:all versions
Mdm9206 FirmwareOperating system
Affected:all versions
Mdm9207c 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 Snapdragon chipset model
    Check the device specifications or system information to determine the exact Qualcomm Snapdragon chipset model (Apq8009, Apq8017, Apq8053, Apq8096, Apq8096au, Apq8098, Mdm9206, Mdm9207c, or related variants). This may be found in /proc/cpuinfo on Android devices, or via device documentation/ manufacturer specs.
    Affected if The chipset model matches one of the affected products: Apq8009, Apq8017, Apq8053, Apq8096, Apq8096au, Apq8098, Mdm9206, or Mdm9207c.
  2. Confirm firmware version
    Access the firmware or baseband version information. On Android, this is typically found in Settings > About Phone > Build Number, or via commands like 'getprop' or 'cat /proc/version'. Check for any available firmware version string or modem firmware version.
    Affected if The device runs any firmware version on the affected chipsets, as all versions of these specific chipsets are vulnerable.
  3. Check for OEM security patches
    Verify the Android security patch level in Settings > About Phone > Security Patch Level. Contact the device manufacturer to confirm whether a firmware patch addressing CVE-2019-10517 has been applied.
    Affected if The security patch level is earlier than the date when the vendor released the fix (contact OEM for specific patch dates), or no patch confirmation has been received.
  4. Review firmware update availability
    Check with the device OEM or carrier for available firmware updates. Look for changelogs or security bulletins mentioning CVE-2019-10517 or Qualcomm firmware security fixes.
    Affected if No firmware update addressing this vulnerability has been applied to the device.

A user is affected if their device contains one of the listed Snapdragon chipset models (Apq8009, Apq8017, Apq8053, Apq8096, Apq8096au, Apq8098, Mdm9206, Mdm9207c) and the firmware has not been patched by the OEM/vendor.

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 patches from Qualcomm and device manufacturers. This is a firmware-level issue requiring OTA updates from OEM/device vendors rather than application-level remediation.

Fix this in Apq8009 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,880
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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