CVE-2015-8679: n/a vulnerability

CVE-2015-8679: The Maxim_smartpa_dev driver in Huawei P8 smartphones with software GRA-TL00 before GRA-TL00C01B230, GRA-CL...

The 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.

UnknownCVSS not scoredNot KEV-listedUpdatedAug 6, 2024, 08:29 UTC (UTC+00:00)

Security readout for executives and security teams

This issue affects specific legacy Huawei P8 and Mate S smartphone software builds. A maliciously crafted app can trigger invalid memory access in the Maxim_smartpa_dev driver and crash the device. The provided sources show denial of service only, not data theft or remote compromise. Exposure appears limited to Huawei P8 and Mate S devices running the specific pre-fix firmware builds named in the CVE record. Modern fleets are unlikely to be broadly exposed unless legacy Huawei handsets remain enrolled, unmanaged, or used for operational workflows. Treat this as a targeted legacy mobile risk. It is not evidenced as actively exploited or remotely exploitable, but affected devices can be crashed by a malicious app. Update or retire any matching devices, especially if used by executives, field staff, or regulated workflows. Mitigation focus: Update affected P8 and Mate S devices to the named fixed builds or later.; Check Huawei PSIRT guidance for model-specific update instructions.; Retire unsupported affected devices if updates are unavailable..

Prepared: Jun 13, 2026, 14:44 UTC (UTC+00:00)

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2015-8679 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup

Vulnerability profileCVE Program record

Severity: Unknown
CVSS: Not scored
Known Exploited: No
Published: Apr 7, 2016, 20:00 UTC (UTC+00:00)

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors

0Timeline events

0ADP providers

1Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

CVE List V5 sourceCVE List V5

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus

n/an/an/aListed

Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.