dbcve.org
Mdm9206 FirmwareOperating system · Qualcomm

CVE-2016-10464

HIGH · 7.5 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 →
84/100
Remediation priority · High
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 Mobile and Snapdragon Wear MDM9206, MDM9607, MDM9640, MDM9650, QCA6174A, QCA6574AU, QCA9377, SD 210/SD 212/SD 205, SD 425, SD 600, SD 650/52, SD 808, SD 810, SD 820, and SDX20, lack of input validation for HCI H4 UART packet ID cause system denial of service.

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 denial-of-service vulnerability exists in the HCI H4 UART driver of Qualcomm Snapdragon chipsets due to insufficient validation of packet IDs. An attacker with local or adjacent network access could send malformed HCI packets via UART to cause system crash or reboot.

MitigationApply the Android security patch level released 2018-04-05 or later, which contains the 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
Mdm9206 FirmwareOperating system
Affected:all versions
Mdm9607 FirmwareOperating system
Affected:all versions
Mdm9640 FirmwareOperating system
Affected:all versions
Mdm9650 FirmwareOperating system
Affected:all versions
Qca6174a FirmwareOperating system
Affected:all versions
Qca6574au FirmwareOperating system
Affected:all versions
Sd 210 FirmwareOperating system
Affected:all versions
Sd 212 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
None
Integrity
None
Availability
High

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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 in your device
    Check system information via 'cat /proc/cpuinfo' or 'lspci' for PCIe devices, or check 'dmesg' for boot logs mentioning Qualcomm chip identifiers such as Mdm9206, Mdm9607, Mdm9640, Mdm9650, Qca6174a, Qca6574au, SD210, or SD212
    Affected if The chipset matches any of the affected models: Mdm9206, Mdm9607, Mdm9640, Mdm9650, Qca6174a, Qca6574au, SD210, or SD212
  2. Check if HCI H4 UART driver is loaded and active
    Examine kernel modules and driver status using 'lsmod | grep h4' or check '/sys/kernel/debug/bluetooth/hci0/hdev' if Bluetooth interface is present; look for H4 UART initialization in 'dmesg' output
    Affected if The H4 UART driver is loaded and the HCI UART interface is enumerated as a Bluetooth or HCI device
  3. Verify UART interface accessibility
    Check for UART device nodes in '/dev/ttyHS*' or '/dev/ttyUSB*' that correspond to HCI H4, and verify read/write access using 'ls -la /dev/ttyHS*' or similar path depending on device tree
    Affected if An HCI H4 UART device node exists and is accessible (attacker needs adjacent or local access to this interface)
  4. Confirm firmware version of the affected chipset
    Query the chipset firmware version through vendor-specific diagnostic tools, AT command interfaces (e.g., 'AT+QVERNAME' on Qualcomm modems), or check firmware files in '/lib/firmware/qcom/' or '/vendor/firmware/'
    Affected if The firmware version is any version prior to the 2018-04-05 Android security patch (note: all versions listed are affected)

Your device is affected if it contains any of the listed Qualcomm chipsets (Mdm9206, Mdm9607, Mdm9640, Mdm9650, Qca6174a, Qca6574au, SD210, SD212) with the HCI H4 UART interface enabled and the firmware predates the April 2018 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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the Android security patch level released 2018-04-05 or later, which contains the fix for this vulnerability in the affected Qualcomm chipset drivers.

Fix this in Mdm9206 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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