CVE-2015-8680
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 · uneditedThe Graphics driver in Huawei P8 smartphones with software GRA-TL00 before GRA-TL00C01B230, GRA-CL00 before GRA-CL00C92B230, GRA-CL10 before GRA-CL10C92B230, GRA-UL00 before GRA-UL00C00B230, and GRA-UL10 before GRA-UL10C00B230, and Mate S smartphones with software CRR-TL00 before CRR-TL00C01B160SP01, CRR-UL00 before CRR-UL00C00B160, and CRR-CL00 before CRR-CL00C92B161 allows attackers to cause a denial of service (system crash) or gain privileges via a crafted application with the graphics permission, aka an "interface access control vulnerability," a different vulnerability than CVE-2015-8307.
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 confidenceA graphics driver vulnerability in Huawei P8 and Mate S smartphones allows a crafted application with graphics permission to trigger either a system crash (denial of service) or privilege escalation. The issue is an interface access control flaw in the graphics driver that fails to properly validate or restrict access to privileged operations.
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 versions= gra-cl00= gra-cl10= gra-tl00= gra-ul00= gra-ul10= crr-cl00= crr-tl00= crr-ul00CVSS 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 your Huawei device modelGo to Settings > About Phone > Model Number (or use *#*#2846579#*#* to access service menu)Affected if Device model is Huawei P8 or Mate S
-
Check the firmware build numberGo to Settings > About Phone > Build Number, or run 'getprop ro.build.display.id' via ADB shellAffected if Build number is earlier than GRA-TL00C01B230 (P8) or CRR-TL00C01B160SP01 (Mate S)
-
Verify the specific firmware variant for P8Run 'getprop ro.product.name' or 'getprop ro.build.version.emui' via ADB shell to identify the gra- variantAffected if Variant is gra-cl00, gra-cl10, gra-tl00, gra-ul00, or gra-ul10 and the build is not in the patched versions listed
-
Verify the specific firmware variant for Mate SRun 'getprop ro.product.name' or 'getprop ro.build.version.emui' via ADB shell to identify the crr variantAffected if Variant is crr-cl00, crr-tl00, or crr-ul00 and the build is not in the patched versions listed
You are affected if you own a Huawei P8 or Mate S device running firmware versions earlier than the patched releases specified for your model variant.
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 the vendor-provided firmware updates that address this vulnerability - for P8 models update to GRA-TL00C01B230, GRA-CL00C92B230, GRA-CL10C92B230, GRA-UL00C00B230, or GRA-UL10C00B230 and later; for Mate S update to CRR-TL00C01B160SP01, CRR-UL00C00B160, or CRR-CL00C92B161 and later.
- 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-2015-8680 — 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-2015-8680 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