CVE-2017-15316
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 GPU driver of Mate 9 Huawei smart phones with software before MHA-AL00B 8.0.0.334(C00) and Mate 9 Pro Huawei smart phones with software before LON-AL00B 8.0.0.334(C00) has a memory double free vulnerability. An attacker tricks a user into installing a malicious application, and the application can call special API, which triggers double free and causes a system crash or arbitrary code execution.
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 confidenceDouble-free vulnerability in the GPU driver of Huawei Mate 9 (MHA-AL00B) and Mate 9 Pro (LON-AL00B) smartphones running software versions prior to 8.0.0.334(C00). A malicious application can trigger the double-free condition through specific API calls, leading to system crash or potential arbitrary code execution.
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< mha-al00b_8.0.0.334\(c00\)< lon-al00b_8.0.0.334\(c00\)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
- 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 device model numberGo to Settings > About Phone > Model Number (or Model) and record the exact model identifierAffected if Model number is MHA-AL00B (Mate 9) or LON-AL00B (Mate 9 Pro)
-
Check firmware versionGo to Settings > About Phone > Version > Build Number (or Settings > System > About Phone > EMUI Version) to find the installed software/firmware versionAffected if Version is earlier than 8.0.0.334(C00)
-
Confirm the full build identifierIn Settings > About Phone, look for the complete build string (e.g., MHA-AL00B 8.0.0.334(C00)) and note the exact numeric version before 8.0.0.334Affected if Build number shows a version lower than 334 in the 8.0.0.x series, or the build string contains a letter (C00) version earlier than C00
-
Verify GPU driver componentThis vulnerability exists in the GPU driver; however, direct inspection of driver version is not accessible through standard user settings. The primary detection relies on firmware version in step 2Affected if Unable to verify GPU driver version separately - firmware version check is the primary indicator
Device is affected if it is a Huawei Mate 9 (MHA-AL00B) or Mate 9 Pro (LON-AL00B) running firmware versions earlier than 8.0.0.334(C00).
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 dataUpdate Mate 9 devices to software version MHA-AL00B 8.0.0.334(C00) or later, and Mate 9 Pro devices to LON-AL00B 8.0.0.334(C00) or later. Users should avoid installing applications from untrusted sources.
- 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-2017-15316 — 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-2017-15316 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