CVE-2017-17173
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 · uneditedDue to insufficient parameters verification GPU driver of Mate 9 Pro Huawei smart phones with the versions before LON-AL00B 8.0.0.356(C00) has an arbitrary memory free vulnerability. An attacker can tricks a user into installing a malicious application on the smart phone, and send given parameter to driver to release special kernel memory resource. Successful exploit may result in phone 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 confidenceThe Huawei Mate 9 Pro GPU driver contains an arbitrary memory free vulnerability due to insufficient parameter validation. A malicious application can send crafted parameters to the GPU driver to trigger release of specific kernel memory resources, potentially causing a kernel panic (phone crash) or enabling arbitrary code execution at the kernel privilege level.
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< lon-al00b_8.0.0.356\(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.
-
Confirm device model is Huawei Mate 9 ProNavigate to Settings > About Phone on the device and verify the model name matches 'Mate 9 Pro' or the model number 'LON-AL00'Affected if Device model is not Huawei Mate 9 Pro, the vulnerability does not apply to this device
-
Locate the firmware versionNavigate to Settings > About Phone > Version on the device to view the installed firmware build numberAffected if Firmware version cannot be determined or is not visible in the About Phone section
-
Compare firmware version against affected rangeCompare the installed firmware build number to the affected version threshold: lon-al00b_8.0.0.356(c00). Versions below this threshold (earlier builds) are affectedAffected if Installed firmware version is lon-al00b_8.0.0.356(c00) or any later version - the device is NOT affected. Any version below this threshold indicates the device IS affected
-
Verify GPU driver is activeCheck if the device boots normally and the GPU/graphics subsystem is operational. On affected devices, the vulnerability would trigger when a malicious application sends crafted parameters to the GPU driverAffected if GPU driver is not loaded or the device does not boot, the specific exploitation pathway cannot be tested; however the vulnerable code still exists in the firmware if version is below the threshold
If the device is a Huawei Mate 9 Pro (LON-AL00) running firmware version lon-al00b_8.0.0.356(c00) or later, the device is NOT affected by this CVE; any earlier firmware version indicates the device IS affected.
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 the device firmware to version LON-AL00B 8.0.0.356(C00) or later to obtain the patched GPU driver. As a defense-in-depth measure, avoid installing applications from untrusted sources.
- Consultation1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-17173 — 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-17173 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