CVE-2016-10299
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 · uneditedAn elevation of privilege vulnerability in Qualcomm closed source components. Product: Android. Versions: Android kernel. Android ID: A-32577244.
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 confidenceThis is a privilege escalation vulnerability in Qualcomm's closed-source kernel components for Android devices. The vulnerability allows an attacker to gain elevated (kernel-level) privileges, potentially leading to full device compromise. The CVSS 9.8 indicates the exploit is easily achievable and has low complexity.
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 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.
-
Check the Android security patch levelNavigate to Settings > About Phone > Security Patch Level, or run 'adb shell getprop ro.build.version.security_patch'Affected if The security patch level is earlier than March 2017, shows no date, or cannot be determined
-
Verify the kernel versionRun 'adb shell uname -r' or check Settings > About Phone > Kernel VersionAffected if The kernel version corresponds to an Android release predating the March 2017 security update
-
Confirm OEM patch availabilityCheck the device manufacturer's security update documentation or contact the OEM directly for the specific device modelAffected if The device model has not received or is not scheduled to receive the March 2017 Android security bulletin patch
A device is affected if it lacks the March 2017 or later Android security patch level, as this vulnerability exists in all Android versions until that specific patch is applied.
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 Android security patches from the device OEM; this vulnerability is patched through the monthly Android security bulletin. Users should ensure their devices receive the March 2017 or later security patch level.
Apply the appropriate Android monthly security patch (this vulnerability was addressed in the July 2017 Android Security Bulletin - refer to source.android.com/security/bulletin)
- 1. Check your Android device's current security patch level in Settings > Security > Security patch level
- 2. Identify your device manufacturer and carrier (if applicable)
- 3. Contact your device manufacturer or carrier to request the security update addressing CVE-2016-10299
- 4. Apply the security update once available from your OEM or carrier
- 5. Verify the security patch level has been updated to include the fix for this vulnerability
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation8.0 h
- Implementation16.0 h
- Testing12.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $11,776.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-10299 — 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-10299 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