CVE-2015-8679
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 Maxim_smartpa_dev driver in Huawei P8 smartphones with software GRA-TL00 before GRA-TL00C01B230, GRA-CL00 before GRA-CL00C92B230, GRA-CL10 before GRA-CL10C92B230, GRA-UL00 before GRA-UL00C00B230, and GRA-UL10 before GRA-UL10C00B230 and Mate S smartphones with software CRR-TL00 before CRR-TL00C01B160SP01, CRR-UL00 before CRR-UL00C00B160, and CRR-CL00 before CRR-CL00C92B161 allow attackers to cause a denial of service (system crash) via a crafted application, which triggers an invalid memory access.
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 denial of service vulnerability exists in the Maxim_smartpa_dev audio driver on Huawei P8 and Mate S smartphones. A locally-installed malicious application can trigger invalid memory access in the driver, causing the device to crash. The vulnerability stems from insufficient input validation when the application interacts with the driver interface.
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= crr-cl00= crr-tl00= crr-ul00= gra-cl00= gra-cl10= gra-tl00= gra-ul00= gra-ul10CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify device model and firmware versionGo to Settings > About Phone on the Huawei device and record the Model Number and Build Number/Firmware versionAffected if The model matches crr-cl00, crr-tl00, crr-ul00 (Mate S) or gra-cl00, gra-cl10, gra-tl00, gra-ul00, gra-ul10 (P8)
-
Confirm Maxim_smartpa_dev driver presenceCheck if the driver module exists on the device by examining /dev/ or /system/lib/modules/ for Maxim_smartpa_dev, or use a terminal to run 'ls -la /dev/maxim*'Affected if The Maxim_smartpa_dev driver interface is present and accessible on the device
-
Compare firmware version to patched releasesCompare your installed build number against known patched versions: P8 should be GRA-TL00C01B230 or later; Mate S should be CRR-TL00C01B160SP01 or laterAffected if The firmware version is older than these patched releases, meaning the input validation fix has not been applied
You are affected if your device is a Huawei P8 or Mate S matching the affected firmware codes AND the Maxim_smartpa_dev driver is present AND your build number is older than the patched versions specified.
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 affected Huawei P8 and Mate S devices to the patched software versions (GRA-TL00C01B230 or later for P8; CRR-TL00C01B160SP01 or later for Mate S). If updates are unavailable, consider disabling or removing the Maxim_smartpa driver if the smart PA functionality is not required.
- Consultation2.0 h
- Implementation1.0 h
- Testing2.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,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-8679 — 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-2015-8679 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