dbcve.org
AndroidOperating system · Google

CVE-2016-10332

MEDIUM · 5.5 CVSS v3.0 Published 2017-06-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
58/100
Remediation priority · Elevated
No privileges

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 all Android releases from CAF using the Linux kernel, stack protection was not enabled for secure applications.

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

In Android releases from CAF (Code Aurora Forum - Qualcomm-based devices), stack protection (stack canaries/smashing protection) was not enabled in the kernel configuration for secure applications. This means buffer overflows in privileged or trusted applications cannot be detected at runtime, potentially allowing exploitation of memory corruption vulnerabilities to escalate privileges or compromise secure processes.

MitigationEnable kernel stack protection (CONFIG_STACKPROTECTOR, CONFIG_STACKPROTECTOR_STRONG) in the kernel build configuration and rebuild the kernel with this protection enabled. End users should await firmware updates from their device OEMs.

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
AndroidOperating 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
Local
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N

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. Check for kernel stack protector configuration
    On a rooted device or device with root access, examine the kernel config file. Try: cat /proc/config.gz 2>/dev/null | gunzip | grep -E 'CONFIG_STACKPROTECTOR' OR check /boot/config-$(uname -r) if available
    Affected if The output does not show CONFIG_STACKPROTECTOR or CONFIG_STACKPROTECTOR_STRONG set to 'y' or 'strong' (the kernel was built without stack protection)
  2. Check kernel command line for stack protector flags
    Examine /proc/cmdline for stack protector-related flags such as 'stackprotector=' or 'stack_guard' parameters. Run: cat /proc/cmdline
    Affected if No stack protector kernel parameters are present in the command line
  3. Verify if kernel was compiled with stack protection
    For device manufacturers or those with access to kernel build files, examine the .config file used to build the kernel image. Look for CONFIG_STACKPROTECTOR and CONFIG_STACKPROTECTOR_STRONG settings
    Affected if These config options are set to 'n', commented out, or absent entirely in the kernel configuration
  4. Check system libraries for stack protector symbols
    On a rooted device, use readelf or check system libraries for stack_chk symbols: readelf -s /system/lib/libc.so | grep stack_chk OR ls /system/lib/* 2>/dev/null | xargs -I {} readelf -s {} 2>/dev/null | grep -i stack
    Affected if No stack checking symbols are found in libc or other system libraries, indicating stack protection was not compiled into the system libraries
  5. Determine if running a custom or OEM kernel without protection
    Identify the kernel version and source: cat /proc/version or check /sys/kernel/version. If using a custom ROM or OEM build, locate the kernel source or configuration used for that build
    Affected if The kernel build configuration cannot be verified as having stack protection enabled, or was built without CONFIG_STACKPROTECTOR

A device is affected if its kernel was built without stack protection (CONFIG_STACKPROTECTOR or CONFIG_STACKPROTECTOR_STRONG not enabled in the kernel configuration), which requires examining the kernel config or build files since this is a compile-time setting, not a runtime toggle.

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

Enable kernel stack protection (CONFIG_STACKPROTECTOR, CONFIG_STACKPROTECTOR_STRONG) in the kernel build configuration and rebuild the kernel with this protection enabled. End users should await firmware updates from their device OEMs.

Fix this in Android Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA8.0 h
44.0 hours of engineering $7,720
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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