CVE-2016-8761
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 · uneditedVideo 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 stack 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 · moderate confidenceStack overflow vulnerability in the video driver of Huawei P9 (before EVA-AL10C00B192) and Honor 6 (before H60-L02_6.10.1) phones allows local attackers to potentially crash the system or escalate privileges to root-level access.
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 the device modelGo to Settings > About Phone > Model Number (or use 'getprop ro.product.model' via ADB)Affected if The model is not Huawei P9, P9 Plus, or Honor 6
-
Check the device's build numberGo to Settings > About Phone > Build Number (or use 'getprop ro.build.display.id' via ADB)Affected if The device is a Huawei P9, P9 Plus, or Honor 6 and the build number cannot be verified against the fixed versions
-
Compare firmware version against fixed buildsFor P9: check if build is before EVA-AL10C00B192. For Honor 6: check if build is before H60-L02_6.10.1. Use 'getprop ro.build.version.emui' for EMUI version.Affected if The installed firmware version is earlier than EVA-AL10C00B192 for P9/P9 Plus, or earlier than H60-L02_6.10.1 for Honor 6
-
Verify video driver module presenceCheck /system/lib/modules/ for video driver files or use 'lsmod' via ADB shell to list loaded kernel modulesAffected if A video driver module is loaded on an affected device model running vulnerable firmware
The device is affected if it is a Huawei P9, P9 Plus, or Honor 6 running firmware versions earlier than EVA-AL10C00B192 (P9/P9 Plus) or H60-L02_6.10.1 (Honor 6).
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-supplied OTA firmware updates to upgrade to the fixed software versions; prior to patching, restrict device access to trusted users and monitor for unusual system behavior.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-8761 — 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-8761 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