dbcve.org
Sd 410 FirmwareOperating system · Qualcomm

CVE-2016-10426

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 430, SD 450, SD 617, SD 625, SD 650/52, SD 810, SD 820, and SD 820A, a buffer overflow can occur in SafeSwitch.

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 buffer overflow vulnerability exists in the SafeSwitch component of multiple Qualcomm Snapdragon mobile and automotive processors (SD 410/12, SD 425, SD 430, SD 450, SD 617, SD 625, SD 650/52, SD 810, SD 820, SD 820A). SafeSwitch manages secure boot functionality, and the buffer overflow could allow attackers to execute arbitrary code or escalate privileges at the firmware level.

MitigationApply Android security patches from 2018-04-05 or later; contact device OEMs for firmware updates as this is a chipset-level vulnerability requiring vendor-specific patches.

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 617 FirmwareOperating system
Affected:all versions
Sd 625 FirmwareOperating system
Affected:all versions
Sd 650 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 Qualcomm Snapdragon chipset model
    On Android, go to Settings > About Phone > Chipset or processor information. Alternatively, use terminal command 'cat /proc/cpuinfo' or 'getprop ro.hardware' to retrieve chipset details.
    Affected if The chipset model matches any of: SD 410, SD 412, SD 425, SD 430, SD 450, SD 617, SD 625, or SD 650.
  2. Verify the SafeSwitch component is present
    SafeSwitch is a firmware-level component managing secure boot. Check device diagnostic logs or bootloader information for SafeSwitch status. On supported devices, examine '/proc/secureboot' or bootloader unlock status if available.
    Affected if SafeSwitch is present and manages secure boot functionality on the device.
  3. Check the current firmware version
    Access the baseband or modem firmware version via Settings > About Phone > Baseband version, or use 'getprop gsm.version.baseband' in terminal. For bootloader-level firmware, consult device-specific diagnostic tools or OEM service menus.
    Affected if The firmware version is any version (the advisory states all versions of the listed chipsets are affected).
  4. Confirm the Android security patch level
    Go to Settings > About Phone > Android security patch level, or run 'getprop ro.build.version.security_patch' in terminal.
    Affected if The security patch level is earlier than 2018-04-05, indicating the device has not received the mitigating patch.

A user is affected if their device uses a vulnerable Snapdragon chipset (SD 410/412/425/430/450/617/625/650) and has not received the 2018-04-05 or later Android security update.

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 patches from 2018-04-05 or later; contact device OEMs for firmware updates as this is a chipset-level vulnerability requiring vendor-specific patches.

Recommended fix Moderate confidence

Android security patch level April 2018 or later (e.g., March 2018, April 2018 security bulletin and beyond)

  1. Identify your specific device model and manufacturer
  2. Check if your device manufacturer has released an Android security patch update for April 2018 or later
  3. If available, apply the latest Android security patch update through your device's system settings > About phone > System updates
  4. If no update is available from your manufacturer, contact the device vendor to request the security patch
Caveat Firmware updates for older devices may no longer be supported by manufacturers; verify device compatibility before applying updates

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
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,580
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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