dbcve.org
Sd 835 FirmwareOperating system · Qualcomm

CVE-2016-10460

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 Mobile SD 835, SD 845, and SD 850, vendor specific opcodes may not have any packet length validation leading to buffer over-reads.

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 · moderate confidence

Missing packet length validation in vendor-specific opcodes on Qualcomm Snapdragon SD 835, SD 845, and SD 850 processors allows unauthenticated remote attackers to perform buffer over-reads, potentially exposing sensitive memory contents or causing denial of service.

MitigationApply Android security updates from 2018-04-05 or later patch level; users of affected devices should ensure they receive OEM firmware updates addressing this vulnerability.

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
Sd 835 FirmwareOperating system
Affected:all versions
Sd 845 FirmwareOperating system
Affected:all versions
Sd 850 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 processor model
    Check the device specifications or system information to determine if the Snapdragon processor is model SD 835, SD 845, or SD 850. This can typically be found in Settings > About Phone > Processor or through terminal commands like 'cat /proc/cpuinfo' on Android devices.
    Affected if The processor is a Qualcomm Snapdragon SD 835, SD 845, or SD 850.
  2. Determine the firmware version
    Check the firmware version installed on the affected processor. On Android devices, this is typically found in Settings > About Phone > Build Number or by running 'getprop ro.build.version.security_patch' in a terminal emulator.
    Affected if The device has any firmware version installed on the SD 835, SD 845, or SD 850 processors.
  3. Verify the security patch level
    Check the Android security patch level date. This is visible in Settings > About Phone > Android security patch level or can be retrieved via 'getprop ro.build.version.security_patch' command.
    Affected if The security patch level is earlier than 2018-04-05, meaning the vulnerability has not been addressed.
  4. Confirm vendor-specific opcode handling is enabled
    The vulnerability exists in vendor-specific opcode handling within the processor firmware. Check if the device firmware supports or utilizes these opcodes, which is inherent to normal operation on affected Snapdragon variants.
    Affected if The device actively uses the Snapdragon processor with vendor-specific opcode processing enabled, which is the default operational state.

The device is affected if it contains a Qualcomm Snapdragon SD 835, SD 845, or SD 850 processor with a security patch level earlier than 2018-04-05.

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 Android security updates from 2018-04-05 or later patch level; users of affected devices should ensure they receive OEM firmware updates addressing this vulnerability.

Recommended fix Moderate confidence

Android Security Patch Level 2018-04-05 or later (contact device manufacturer for specific firmware version)

  1. Check your device's current Android security patch level in Settings > About Phone > Software Info > Security patch level
  2. If the security patch level is earlier than April 5, 2018, check for system updates via Settings > System > Software Update or Settings > About Phone > System Updates
  3. Apply the latest available Android system update from your device manufacturer
  4. After updating, verify the security patch level shows April 2018 or later
Caveat Security updates are generally low-risk; consult your device manufacturer's release notes for any known issues

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

Fix this in Sd 835 Firmware Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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