dbcve.org
Mdm9206 FirmwareOperating system · Qualcomm

CVE-2017-18140

CRITICAL · 9.8 CVSS v3.0 Published 2018-04-11
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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
In Android before security patch level 2018-04-05 on Qualcomm Snapdragon Automobile, Snapdragon Mobile, and Snapdragon Wear MDM9206, MDM9607, MDM9650, MSM8909W, SD 210/SD 212/SD 205, SD 400, SD 425, SD 430, SD 450, SD 615/16/SD 415, SD 617, SD 625, SD 650/52, SD 808, SD 810, SD 820, SD 820A, SD 835, SD 845, when processing a call disconnection, there is an attempt to print the RIL token-id to the debug log. If eMBMS service is enabled while processing the call disconnect, a Use After Free condition may potentially occur.

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 Qualcomm Radio Interface Layer (RIL) when processing call disconnection events. If enhanced Multimedia Broadcast Multicast Service (eMBMS) is enabled during call disconnect, the code attempts to print a RIL token-id to debug log after the token memory has been freed, leading to UAF. This affects multiple Snapdragon chipset generations used in mobile, automotive, and wearable devices.

MitigationApply the Android security patch level 2018-04-05 or later. Since this is a baseband firmware vulnerability in Qualcomm chipsets, organizations should inventory affected devices, verify OEM firmware update availability, and prioritize patching. Until patches are available, consider disabling eMBMS services if feasible and monitor for exploitation indicators.

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
Mdm9206 FirmwareOperating system
Affected:all versions
Mdm9607 FirmwareOperating system
Affected:all versions
Mdm9650 FirmwareOperating system
Affected:all versions
Msm8909w FirmwareOperating system
Affected:all versions
Sd 210 FirmwareOperating system
Affected:all versions
Sd 212 FirmwareOperating system
Affected:all versions
Sd 205 FirmwareOperating system
Affected:all versions
Sd 400 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
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:N/AC:L/PR:N/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
    Query device information via AT commands (AT+CGMM or AT+CGMI) or check Settings > About Phone > Model/Hardware to determine the chipset. For automotive/IoT devices, consult the hardware specifications or BOM documentation.
    Affected if Device uses Mdm9206, Mdm9607, Mdm9650, Msm8909w, Sd 210, Sd 212, Sd 205, or Sd 400 chipset
  2. Confirm eMBMS is enabled
    Check device network configuration for eMBMS status. This may be in Settings > Mobile Networks > eMBMS, carrier settings, or via AT command query. Look for any active eMBMS subscriptions or multicast bearers.
    Affected if eMBMS is enabled and active on the device at the time of call disconnection events
  3. Check Android security patch level
    Navigate to Settings > About Phone > Software Information > Security Patch Level to view the installed patch date.
    Affected if Security Patch Level is earlier than April 5, 2018

A device is affected if it uses one of the listed Qualcomm chipsets AND has eMBMS enabled AND has not received the 2018-04-05 or later security patch.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the Android security patch level 2018-04-05 or later. Since this is a baseband firmware vulnerability in Qualcomm chipsets, organizations should inventory affected devices, verify OEM firmware update availability, and prioritize patching. Until patches are available, consider disabling eMBMS services if feasible and monitor for exploitation indicators.

Recommended fix High confidence

Android Security Patch Level 2018-04-05 or later

  1. Update the device to Android security patch level 2018-04-05 or later, which includes the fix for this Qualcomm Snapdragon firmware vulnerability
  2. Apply the monthly Android security update from your device manufacturer that contains the CVE-2017-18140 fix
  3. Verify the security patch level by going to Settings > About Phone > Security Patch Level and confirm it shows April 2018 or later
Caveat Minimal - security patches typically have no breaking changes; ensure device is charged before updating

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Mdm9206 Firmware Scoped from the published advisory
  • Consultation8.0 h
  • Implementation2.0 h
  • Testing6.0 h
  • Review / QA4.0 h
20.0 hours of engineering $3,580
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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