dbcve.org
Mdm9206 FirmwareOperating system · Qualcomm

CVE-2016-10437

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 Small Cell SoC, Snapdragon Mobile, and Snapdragon Wear FSM9055, MDM9206, MDM9607, MDM9635M, MDM9640, MDM9650, MSM8909W, SD 210/SD 212/SD 205, SD 400, SD 410/12, 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 835, and SDX20, while logging debug statements or ftrace events from rmnet_data, the socket buffer function uses normal format specifiers which may result in information exposure.

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 format string vulnerability exists in the rmnet_data component's logging functionality on affected Qualcomm Snapdragon and MDM chipsets. The socket buffer function uses normal format specifiers when logging debug statements or ftrace events, which can lead to information exposure through debug logs.

MitigationApply the Android security patch level from 2018-04-05 or later, which contains the fix for this format string vulnerability in the rmnet_data component.

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
Fsm9055 FirmwareOperating system
Affected:all versions
Mdm9635m FirmwareOperating system
Affected:all versions
Mdm9640 FirmwareOperating system
Affected:all versions
Mdm9650 FirmwareOperating system
Affected:all versions
Msm8909w FirmwareOperating system
Affected:all versions
Sd 210 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
None
Availability
None

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

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 chipset model
    Run 'cat /proc/cpuinfo' or check 'ls /sys/class/net' for interface names, or use 'getprop' commands on Android to retrieve hardware details (e.g., 'getprop ro.hardware', 'getprop ro.product.device')
    Affected if The chipset matches any of: Mdm9206, Mdm9607, Fsm9055, Mdm9635m, Mdm9640, Mdm9650, Msm8909w, or Sd 210
  2. Check firmware version
    Retrieve firmware version via 'getprop' (e.g., 'getprop ro.build.version.all') or check '/proc/version' or 'cat /sys/class/dmi/id/product_version' depending on the platform
    Affected if The firmware version is any version on the affected chipsets (all versions of the listed products are affected)
  3. Verify rmnet_data component presence
    Check if the rmnet_data module is loaded or present on the system: 'ls /system/lib/modules/rmnet*' or 'ls /vendor/lib/modules/rmnet*' or check 'cat /proc/modules' for rmnet_data
    Affected if The rmnet_data module is loaded or exists on the system
  4. Check debug logging configuration
    Examine if debug logging is enabled for the rmnet_data component. Check for presence of debug nodes like '/sys/kernel/debug/rmnet*' or review 'logcat' output for rmnet_data debug messages. Also check 'getprop' for debug properties (e.g., 'getprop | grep rmnet')
    Affected if Debug logging or ftrace events are enabled for rmnet_data, as the vulnerability manifests when debug statements with improper format specifiers are logged

A system is affected if it uses any of the listed Qualcomm chipsets (Mdm9206, Mdm9607, Fsm9055, Mdm9635m, Mdm9640, Mdm9650, Msm8909w, Sd 210) and has the rmnet_data component with debug logging enabled, since all firmware versions of these products contain the format string vulnerability in rmnet_data's logging functionality.

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 from 2018-04-05 or later, which contains the fix for this format string vulnerability in the rmnet_data component.

Fix this in Mdm9206 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,970
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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