CVE-2016-8760
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 · uneditedTouchscreen driver in Huawei P9 phones with software versions before EVA-AL10C00B192 and Huawei Honor 6 phones with software versions before H60-L02_6.10.1 has a heap overflow vulnerability, which allows attackers to crash the system or escalate user privilege.
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 confidenceHeap overflow vulnerability in the touchscreen driver of Huawei P9 (before EVA-AL10C00B192) and Honor 6 (before H60-L02_6.10.1) allows attackers to crash the system or escalate user privileges via memory corruption.
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 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
- Local
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:L/AC:L/PR:N/UI:R/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 device modelCheck the device settings or use 'getprop ro.product.model' command in ADB to confirm the device is a Huawei P9, P9 Plus, or Honor 6Affected if Device model is Huawei P9, P9 Plus, or Honor 6
-
Retrieve firmware build versionUse 'getprop ro.build.display.id' or check Settings > About Phone > Build Number to obtain the exact firmware version stringAffected if Firmware version is earlier than EVA-AL10C00B192 for P9/P9 Plus, or earlier than H60-L02_6.10.1 for Honor 6, or if the version string cannot be determined
-
Confirm touchscreen module is loadedVerify the touchscreen driver is active by checking 'getprop hw.mtp.enabled' or inspecting /proc/bus/input/devices for touchscreen input handlersAffected if Touchscreen input device is present and active (this is the default state for these phones)
-
Compare to fixed version baselineCompare your retrieved firmware version against the known fixed builds: EVA-AL10C00B192 or later for P9/P9 Plus, H60-L02_6.10.1 or later for Honor 6Affected if Installed version is below these thresholds
You are affected if you are using a Huawei P9, P9 Plus, or Honor 6 device with firmware version below EVA-AL10C00B192 (P9/P9 Plus) or below H60-L02_6.10.1 (Honor 6), and the touchscreen driver is active (which is the default).
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.
From vendor dataApply vendor firmware updates (EVA-AL10C00B192+ for P9, H60-L02_6.10.1+ for Honor 6) to patch the touchscreen driver; no workarounds available for this kernel-level driver vulnerability.
- Consultation4.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,352.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-8760 — 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-8760 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