CVE-2017-8141
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 Touch Panel (TP) driver in P10 Plus smart phones with software versions earlier than VKY-AL00C00B153 has a memory double free vulnerability. An attacker with the root privilege of the Android system tricks a user into installing a malicious application, and the application can start multiple threads and try to free specific memory, which could 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 confidenceA memory double-free vulnerability exists in the Touch Panel (TP) driver of Huawei P10 Plus smartphones running software versions earlier than VKY-AL00C00B153. An attacker with Android root privileges can install a malicious application that spawns multiple threads to trigger the double free, causing system crash or potentially enabling 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< vky-al00c00b153CVSS 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 P10 PlusCheck the device settings: Settings > About Phone > Model Number, or run `getprop ro.product.model` via ADB shellAffected if Model number is not Huawei P10 Plus (e.g., VKY-L09, L29, or other models)
-
Check firmware build numberNavigate to Settings > About Phone > Build Number, or run `getprop ro.build.display.id` via ADB shellAffected if Build number is lexicographically or numerically earlier than VKY-AL00C00B153 (e.g., VKY-AL00C00B150, B140, etc.)
-
Verify exact firmware version stringRun `getprop ro.build.version.emui` or check Settings > About Phone > EMUI version to get the full version stringAffected if Version string indicates software earlier than VKY-AL00C00B153
-
Determine if root privileges are presentCheck using a root checker app, or attempt to run `su` command via ADB shell to see if root access is grantedAffected if Device has root access enabled (root shell is obtainable without permission denial)
-
Assess application installation policyCheck if 'Unknown sources' or 'Install unknown apps' is enabled in Settings > Security, or if the device allows sideloading APKs from non-Huawei AppGallery sourcesAffected if Unknown sources are enabled, allowing installation of apps outside the official app store
You are affected if you own a Huawei P10 Plus with firmware version earlier than VKY-AL00C00B153 and your device either has root access or allows installation of untrusted applications.
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 Huawei P10 Plus firmware to version VKY-AL00C00B153 or later, which contains the patched TP driver. Users should avoid installing applications from untrusted sources and ensure device software remains current.
- Consultation1.0 h
- Testing1.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-8141 — 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-8141 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