dbcve.org
Mate S FirmwareApplication · Huawei

CVE-2015-8682

MEDIUM · 6.1 CVSS v3.0 Published 2016-04-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
64/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
The Video0 driver in Huawei P8 smartphones with software GRA-UL00 before GRA-UL00C00B350, GRA-UL10 before GRA-UL10C00B350, GRA-TL00 before GRA-TL00C01B350, GRA-CL00 before GRA-CL00C92B350, and GRA-CL10 before GRA-CL10C92B350 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 obtain sensitive information from stack memory or cause a denial of service (system crash) via a crafted application, which triggers an invalid memory access.

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

A vulnerability exists in the Video0 driver in Huawei P8 and Mate S smartphones that allows a malicious application to trigger invalid memory access, resulting in disclosure of sensitive data from kernel stack memory or causing a system crash (denial of service). The issue stems from improper input validation or memory handling in the driver when processing certain operations initiated by applications.

MitigationApply vendor-supplied firmware updates (GRA-UL00C00B350 or later, GRA-UL10C00B350 or later, GRA-TL00C01B350 or later, GRA-CL00C92B350 or later, GRA-CL10C92B350 or later for P8; CRR-TL00C01B160SP01 or later, CRR-UL00C00B160 or later, CRR-CL00C92B161 or later for Mate S). If updates are unavailable, restrict application permissions and monitor for suspicious applications.

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
Mate S FirmwareApplication
Affected:<= crr-cl00c92b153<= crr-tl00c01b153sp01<= crr-ul00c00b153
P8 FirmwareApplication
Affected:<= gra-cl00c92b230<= gra-cl10c92b230<= gra-tl00c01b230<= gra-ul00c00b230<= gra-ul10c00b230

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
Low
Integrity
None
Availability
High

CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:L/I:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify device model
    Check if the device is Huawei P8 or Mate S by going to Settings > About Phone and looking at the model number
    Affected if Device model is Huawei P8 or Mate S - proceed to next check
  2. Check P8 firmware version
    In Settings > About Phone > Version, look for the build number (e.g., gra-cl00c92b230). Compare the numeric portion to the affected ranges: CL00/CL10 versions <= c92b230, TL00 versions <= c01b230, UL00 versions <= c00b230, UL10 versions <= c00b230
    Affected if P8 firmware version falls at or below any of these thresholds: gra-cl00c92b230, gra-cl10c92b230, gra-tl00c01b230, gra-ul00c00b230, gra-ul10c00b230 - device is affected
  3. Check Mate S firmware version
    In Settings > About Phone > Version, look for the build number (e.g., crr-cl00c92b153). Compare to affected versions: CL00 versions <= c92b153, TL00 versions <= c01b153sp01, UL00 versions <= c00b153
    Affected if Mate S firmware version falls at or below any of these thresholds: crr-cl00c92b153, crr-tl00c01b153sp01, crr-ul00c00b153 - device is affected

Device is affected if it is a Huawei P8 or Mate S running firmware at or below the version thresholds listed above.

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

Apply vendor-supplied firmware updates (GRA-UL00C00B350 or later, GRA-UL10C00B350 or later, GRA-TL00C01B350 or later, GRA-CL00C92B350 or later, GRA-CL10C92B350 or later for P8; CRR-TL00C01B160SP01 or later, CRR-UL00C00B160 or later, CRR-CL00C92B161 or later for Mate S). If updates are unavailable, restrict application permissions and monitor for suspicious applications.

Fix this in Mate S Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,120
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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