dbcve.org
Sd 410 FirmwareOperating system · Qualcomm

CVE-2016-10462

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 and Snapdragon Mobile SD 410/12, SD 425, SD 427, SD 430, SD 435, SD 450, SD 615/16/SD 415, SD 625, SD 650/52, SD 808, SD 810, SD 820, SD 820A, SD 835, SDM630, SDM636, SDM660, and Snapdragon_High_Med_2016, the Access Control policy for HLOS allows access to Slimbus, GPU, GIC resources.

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

The Access Control policy for the High-Level Operating System (HLOS) in Qualcomm Snapdragon processors improperly allows access to protected hardware resources including Slimbus (audio subsystem), GPU (graphics processing unit), and GIC (Generic Interrupt Controller). This misconfiguration could allow code executing in the HLOS context to access and potentially manipulate critical hardware resources that should be restricted, leading to privilege escalation or denial of service.

MitigationApply the vendor-supplied security patch level dated 2018-04-05 or later to affected Android devices. This is a firmware-level fix that must be provided by Qualcomm and device manufacturers; there is no user-configurable workaround.

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 410 FirmwareOperating system
Affected:all versions
Sd 412 FirmwareOperating system
Affected:all versions
Sd 425 FirmwareOperating system
Affected:all versions
Sd 430 FirmwareOperating system
Affected:all versions
Sd 450 FirmwareOperating system
Affected:all versions
Sd 615 FirmwareOperating system
Affected:all versions
Sd 616 FirmwareOperating system
Affected:all versions
Sd 415 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 Snapdragon chipset model
    Check the device specifications or use commands like `cat /proc/cpuinfo` on Android devices to identify the processor model
    Affected if Model number matches Sd 410, Sd 412, Sd 425, Sd 430, Sd 450, Sd 615, Sd 616, or Sd 415
  2. Determine the Android security patch level
    On Android devices, go to Settings > About Phone > Security Patch Level, or use `getprop ro.build.version.security_patch`
    Affected if Security patch level is earlier than 2018-04-05 or cannot be determined
  3. Check the vendor firmware version
    Query the bootloader or baseband version using `getprop` commands such as `getprop ro.build.version.all` or `getprop ro.bootimage.build.fingerprint`
    Affected if Firmware version is from before April 2018 and matches affected Snapdragon models

A device is likely affected if it contains an affected Snapdragon model (Sd 410/412/425/430/450/615/616/415) and has a security patch level dated before 2018-04-05, as the access control misconfiguration exists in the firmware and cannot be directly observed without vendor tooling.

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 vendor-supplied security patch level dated 2018-04-05 or later to affected Android devices. This is a firmware-level fix that must be provided by Qualcomm and device manufacturers; there is no user-configurable workaround.

Recommended fix High confidence

Android security patch level April 5, 2018 or later (for affected Snapdragon processors)

  1. 1. Identify the affected device model and verify the current Android security patch level by going to Settings > About Phone > Software Information or checking the Android security patch level displayed in Settings.
  2. 2. Check for available system updates for the device: Go to Settings > System > System Update or Settings > About Phone > System Updates.
  3. 3. Apply the latest Android security update. The fix requires updating to Android with a 2018-04-05 or later security patch level.
  4. 4. After updating, verify the security patch level has been updated to April 2018 or later in Settings > About Phone > Software Information > Security Patch Level.
  5. 5. If the device manufacturer has not released an update with the April 2018 security patch level, contact the device vendor or Qualcomm for a firmware update that includes the access control policy fix.
Caveat Users should ensure they back up important data before applying system updates. Some older devices may no longer receive security updates from manufacturers.

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

Fix this in Sd 410 Firmware Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
36.0 hours of engineering $6,400
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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