dbcve.org
P9 FirmwareOperating system · Huawei

CVE-2016-8764

MEDIUM · 6.4 CVSS v3.0 Published 2017-04-02
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
66/100
Remediation priority · Elevated
Zero-click

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 TrustZone driver in Huawei P9 phones with software Versions earlier than EVA-AL10C00B352 and P9 Lite with software VNS-L21C185B130 and earlier versions and P8 Lite with software ALE-L02C636B150 and earlier versions has an input validation vulnerability, which allows attackers to read and write user-mode memory data anywhere in the TrustZone driver.

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

This is an input validation vulnerability in the TrustZone driver of Huawei P9, P9 Lite, and P8 Lite smartphones. The flaw allows attackers to read and write user-mode memory data anywhere in the TrustZone driver, potentially enabling privilege escalation or memory corruption attacks. TrustZone is a hardware-based security technology that creates a Trusted Execution Environment (TEE) separate from the main OS.

MitigationUpdate affected Huawei P9 (to EVA-AL10C00B352 or later), P9 Lite (to VNS-L21C185B130 or later), and P8 Lite (to ALE-L02C636B150 or later) to the latest vendor-provided software version containing the TrustZone driver patch.

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
P9 FirmwareOperating system
Affected:all versions
P9 Lite FirmwareOperating system
Affected:<= vns-l21c185b130
P8 Lite FirmwareOperating system
Affected:<= ale-l02c636b150

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
High
Privileges
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:L/AC:H/PR:H/UI:N/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 checks

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

  1. Identify your device model
    Check the model number of your Huawei smartphone (typically found in Settings > About Phone). Confirm it is one of: P9, P9 Lite, or P8 Lite.
    Affected if The device is a Huawei P9, P9 Lite, or P8 Lite.
  2. Check P9 firmware version
    On Huawei P9, navigate to Settings > About Phone > Version. Compare the firmware build number against the affected range (all versions are affected).
    Affected if Running any firmware version on Huawei P9.
  3. Check P9 Lite firmware version
    On Huawei P9 Lite, navigate to Settings > About Phone > Version. Compare the build number (e.g., vns-l21c185b130) against the affected range of vns-l21c185b130 or earlier.
    Affected if Running firmware version vns-l21c185b130 or earlier on Huawei P9 Lite.
  4. Check P8 Lite firmware version
    On Huawei P8 Lite, navigate to Settings > About Phone > Version. Compare the build number (e.g., ale-l02c636b150) against the affected range of ale-l02c636b150 or earlier.
    Affected if Running firmware version ale-l02c636b150 or earlier on Huawei P8 Lite.
  5. Verify TrustZone driver presence
    Check if the TrustZone driver is loaded on the device. This may require examining system information or using diagnostic tools that show kernel modules or TEE (Trusted Execution Environment) components.
    Affected if The device has an active TrustZone driver, which is required for the vulnerability to be exploitable.

You are affected if your device is a Huawei P9 (any version), P9 Lite (version vns-l21c185b130 or earlier), or P8 Lite (version ale-l02c636b150 or earlier), and the TrustZone driver is present and enabled.

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

Update affected Huawei P9 (to EVA-AL10C00B352 or later), P9 Lite (to VNS-L21C185B130 or later), and P8 Lite (to ALE-L02C636B150 or later) to the latest vendor-provided software version containing the TrustZone driver patch.

Fix this in P9 Firmware Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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