dbcve.org
Mdm9206 FirmwareOperating system · Qualcomm

CVE-2016-10427

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, MDM9615, MDM9625, MDM9635M, MDM9640, MDM9645, MDM9650, MDM9655, 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 800, SD 808, SD 810, SD 820, SD 835, SD 845, SD 850, and SDX20, improper boundary check in RLC AM module leads to denial of service by reaching assertion.

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

Improper boundary check in the RLC AM (Radio Link Control Acknowledged Mode) module in Qualcomm Snapdragon baseband firmware allows remote attackers to trigger a denial of service via assertion by sending specially crafted RLC packets. This affects multiple mobile and wearable chipsets including MDM9206, MDM9607, SD 820, SD 835, and others.

MitigationApply the 2018-04-05 or later Android security patch level, which contains the vendor-supplied firmware fix for this boundary check vulnerability in the RLC AM module.

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
Mdm9615 FirmwareOperating system
Affected:all versions
Mdm9625 FirmwareOperating system
Affected:all versions
Mdm9635m FirmwareOperating system
Affected:all versions
Mdm9640 FirmwareOperating system
Affected:all versions
Mdm9645 FirmwareOperating system
Affected:all versions
Mdm9650 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 baseband firmware version
    On Android devices, check the baseband version via Settings > About Phone > Baseband version, or run 'getprop gsm.version.baseband' in ADB shell. On other platforms, consult the device's modem/firmware diagnostic interface.
    Affected if The displayed baseband version corresponds to one of the affected MDM models (MDM9206, MDM9607, MDM9615, MDM9625, MDM9635m, MDM9640, MDM9645, MDM9650) and cannot be determined to be a fixed version.
  2. Confirm the chipset model
    Identify the SoC/chipset via 'getprop ro.board.platform' or 'getprop ro.hardware' in ADB shell, or check device specifications. The MDM9206, MDM9607, and other MDM prefixes indicate baseband modem models.
    Affected if The device uses a listed Qualcomm Snapdragon baseband modem (MDM9206, MDM9607, MDM9615, MDM9625, MDM9635m, MDM9640, MDM9645, or MDM9650).
  3. Check the Android security patch level
    On Android devices, go to Settings > About Phone > Android security patch level, or run 'getprop ro.build.version.security_patch' in ADB shell.
    Affected if The security patch level is earlier than 2018-04-05, indicating the firmware fix has not been applied.
  4. Verify RLC AM module activity
    This is a baseband module that processes RLC packets when the cellular radio is active. Check if the device has an active cellular connection or has cellular capability enabled. There is no user-accessible command to directly inspect the RLC AM module state in the baseband.
    Affected if The device has cellular radio functionality enabled and uses an affected baseband firmware, making the boundary check vulnerability present in the RLC AM processing path.

The device is affected if it uses any of the listed Qualcomm MDM baseband firmware versions (MDM9206, MDM9607, MDM9615, MDM9625, MDM9635m, MDM9640, MDM9645, MDM9650) and the Android security patch level is earlier than 2018-04-05, or the firmware version cannot be confirmed as fixed.

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 2018-04-05 or later Android security patch level, which contains the vendor-supplied firmware fix for this boundary check vulnerability in the RLC AM module.

Fix this in Mdm9206 Firmware Scoped from the published advisory
  • Consultation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,030
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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