CVE-2016-10440
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 · uneditedIn Android before 2018-04-05 or earlier security patch level on Qualcomm Snapdragon Mobile SD 425, SD 430, SD 450, SD 625, and SD 650/52, there is improper access control to a bus.
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 confidenceThis is a hardware-level vulnerability in Qualcomm Snapdragon mobile processors (SD 425, SD 430, SD 450, SD 625, SD 650/52) where improper access control to a bus exists. The issue allows potential privilege escalation or unauthorized memory access at the firmware level, enabling an attacker to potentially execute code with elevated privileges or access sensitive data.
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 dataall versionsall versionsall versionsall versionsall versionsall versionsCVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify the Snapdragon processor modelRun 'getprop ro.board.platform' or check /proc/cpuinfo to determine the chipset modelAffected if The model is SD 425, SD 430, SD 450, SD 625, SD 650, or SD 652
-
Check the Android security patch levelRun 'getprop ro.build.version.security_patch' to retrieve the installed security patch dateAffected if The security patch level is earlier than 2018-04-05 or the property is empty/unavailable
-
Verify firmware update availabilityCheck device settings under About Phone > Software Update or contact the device manufacturer for firmware update statusAffected if No security patch dated 2018-04-05 or later has been applied to the device
The device is affected if it contains one of the listed Snapdragon processors (SD 425, 430, 450, 625, 650, 652) AND has not received the Android security patch dated 2018-04-05 or later.
Generated from the published advisory. Verify against your own configuration.
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 · scopedApply the Android security patch level dated 2018-04-05 or later, which contains the vendor-supplied firmware fix for the bus access control issue. Contact device manufacturers for device-specific firmware updates if unavailable through standard OTA updates.
Android devices with security patch level 2018-04-05 or later contain the fix for this vulnerability
- Check current Android security patch level on the device (Settings > About Phone > Security Patch Level)
- Ensure the device receives Android security patch level 2018-04-05 or later
- Apply system updates through Settings > System > Software Update or Settings > About Phone > System Updates
- Verify after update that the Security Patch Level reflects April 2018 or later
- If the device manufacturer has not released an update with the 2018-04-05 patch level, contact the device vendor for firmware/ROM update support
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation12.0 h
- Implementation8.0 h
- Testing24.0 h
- Review / QA12.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $15,360.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-10440 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2016-10440 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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