dbcve.org
P8 FirmwareOperating system · Huawei

CVE-2016-8279

MEDIUM · 5.5 CVSS v3.0 Published 2016-09-26
Fix available
A fix is available. Upgrade to after 6.9 or later.
See remediation →
58/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 video driver in Huawei Mate S smartphones with software CRR-TL00 before CRR-TL00C01B362, CRR-UL20 before CRR-UL20C00B362, CRR-CL00 before CRR-CL00C92B362, and CRR-CL20 before CRR-CL20C92B362; P8 smartphones with software GRA-TL00 before GRA-TL00C01B366, GRA-UL00 before GRA-UL00C00B366, GRA-UL10 before GRA-UL10C00B366, and GRA-CL00 before GRA-CL00C92B366; and Honor 6 and Honor 6 Plus smartphones with software before 6.9.16 allows attackers to cause a denial of service (device reboot) via a crafted application.

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 denial of service vulnerability exists in the video driver of Huawei Mate S, P8, and Honor 6/6 Plus smartphones. A locally-running crafted application can trigger the vulnerability, causing the device to reboot unexpectedly. The vulnerability stems from insufficient input validation or error handling in the video driver component.

MitigationApply the vendor-supplied firmware/driver updates from Huawei for all affected device models and software versions listed in the advisory. Organizations should inventory affected devices and implement a patch management process for mobile devices.

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
P8 FirmwareOperating system
Affected:= gra-cl00= gra-tl00= gra-ul00= gra-ul10
Mate S FirmwareOperating system
Affected:= crr-cl00= crr-cl20= crr-tl00= crr-ul20
Honor6 FirmwareOperating system
Affected:<= 6.9

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

CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:N/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 the device model
    Check the device settings or system information to confirm whether the device is a Huawei Mate S, P8, or Honor 6. On Android, this is typically found under Settings > About Phone > Model Number.
    Affected if The device model is Huawei Mate S, P8, or Honor 6
  2. Determine the firmware build number
    On the device, go to Settings > About Phone > Build Number to locate the specific firmware version installed. This displays the exact build identifier (such as gra-cl00, crr-tl00, or a version number like 6.9).
    Affected if The firmware version matches one of the affected build identifiers or falls within the affected version range
  3. Compare against affected P8 firmware versions
    If the device is a Huawei P8, verify whether the build number equals gra-cl00, gra-tl00, gra-ul00, or gra-ul10. These are the exact affected firmware identifiers.
    Affected if The P8 firmware build number is exactly gra-cl00, gra-tl00, gra-ul00, or gra-ul10
  4. Compare against affected Mate S firmware versions
    If the device is a Huawei Mate S, verify whether the build number equals crr-cl00, crr-cl20, crr-tl00, or crr-ul20. These are the exact affected firmware identifiers.
    Affected if The Mate S firmware build number is exactly crr-cl00, crr-cl20, crr-tl00, or crr-ul20
  5. Compare against affected Honor 6 firmware version
    If the device is a Huawei Honor 6, check the firmware version number. The vulnerability affects version 6.9 and any earlier versions (versions <= 6.9).
    Affected if The Honor 6 firmware version is 6.9 or lower

A device is affected if it is a Huawei Mate S, P8, or Honor 6 with a firmware version matching one of the specific build identifiers listed (gra-*, crr-*, or version <= 6.9 for Honor 6).

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
Upgrade available Upgrade to a release after 6.9
Interim mitigation

Apply the vendor-supplied firmware/driver updates from Huawei for all affected device models and software versions listed in the advisory. Organizations should inventory affected devices and implement a patch management process for mobile devices.

Fix this in P8 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,690
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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