dbcve.org
Mdm9635m FirmwareOperating system · Qualcomm

CVE-2016-10494

CRITICAL · 9.8 CVSS v3.0 Published 2018-04-18
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 2018-04-05 or earlier security patch level on Qualcomm Snapdragon Automobile, Snapdragon Mobile, and Snapdragon Wear MDM9206, MDM9607, MDM9625, MDM9640, MDM9645, MDM9650, MDM9655, MSM8909W, SD 210/SD 212/SD 205, SD 400, SD 425, SD 430, SD 450, SD 617, SD 625, SD 650/52, SD 800, SD 808, SD 810, SD 820, SD 820A, SD 835, SD 845, SD 850, and SDX20, integer overflow may lead to buffer overflows in IPC router Root-PD driver.

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

Integer overflow in the IPC router Root-PD driver of Qualcomm Snapdragon chipsets can lead to buffer overflows, potentially allowing attackers to execute arbitrary code or escalate privileges. This driver-level vulnerability affects multiple Snapdragon generations used in mobile devices, wearables, and automotive systems.

MitigationApply the Android security patch level from April 5, 2018 or later, which contains the vendor fix for this vulnerability in the affected Qualcomm chipset drivers.

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
Mdm9635m FirmwareOperating system
Affected:all versions
Mdm9640 FirmwareOperating system
Affected:all versions
Mdm9645 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
    Check the device specifications or system information to determine the exact Qualcomm Snapdragon chipset (e.g., Mdm9635m, Mdm9640, Mdm9645, Msm8909w, Sd 210, Sd 212, Sd 205, or Sd 400)
    Affected if The chipset model matches one of the following: Mdm9635m, Mdm9640, Mdm9645, Msm8909w, Sd 210, Sd 212, Sd 205, or Sd 400
  2. Check the IPC router driver firmware version
    Access the device's baseband or modem firmware information through diagnostic tools, engineering mode, or by reading /proc/version or similar system files that expose chipset firmware details
    Affected if The driver firmware version cannot be determined or is present on the listed chipset models
  3. Confirm the IPC router Root-PD driver is present
    Verify the existence of the IPC router driver in the kernel or firmware by examining /sys or /proc filesystem entries related to IPC router, or by checking kernel config for CONFIG_IPC_ROUTER
    Affected if The IPC router Root-PD driver is loaded or compiled into the system kernel/firmware
  4. Check Android security patch level
    Go to Settings > About Phone > Android security patch level to view the installed patch date
    Affected if The security patch level is earlier than April 5, 2018

A device is affected if it contains any of the listed Qualcomm chipset models (Mdm9635m, Mdm9640, Mdm9645, Msm8909w, Sd 210, Sd 212, Sd 205, or Sd 400) with the IPC router driver present and a security patch level before April 5, 2018.

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 from April 5, 2018 or later, which contains the vendor fix for this vulnerability in the affected Qualcomm chipset drivers.

Recommended fix High confidence

Android security patch level April 2018 or later (2018-04-05)

  1. Check the current Android security patch level on the affected device in Settings > About Phone > Android security patch level
  2. Update the device to an Android version with security patch level April 2018 or later to receive the fix for this vulnerability
  3. After updating, verify the security patch level has been updated to April 2018 or later in Settings > About Phone > Android security patch level

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

Fix this in Mdm9635m Firmware Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing4.0 h
  • Review / QA3.0 h
10.0 hours of engineering $1,720
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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