CVE-2015-8682: n/a vulnerability

CVE-2015-8682: The Video0 driver in Huawei P8 smartphones with software GRA-UL00 before GRA-UL00C00B350, GRA-UL10 before G...

The Video0 driver in Huawei P8 smartphones with software GRA-UL00 before GRA-UL00C00B350, GRA-UL10 before GRA-UL10C00B350, GRA-TL00 before GRA-TL00C01B350, GRA-CL00 before GRA-CL00C92B350, and GRA-CL10 before GRA-CL10C92B350 and Mate S smartphones with software CRR-TL00 before CRR-TL00C01B160SP01, CRR-UL00 before CRR-UL00C00B160, and CRR-CL00 before CRR-CL00C92B161 allows attackers to obtain sensitive information from stack memory or 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

CVE-2015-8682 affects specific Huawei P8 and Mate S smartphone firmware. A malicious app could make the Video0 driver expose stack-memory data or crash the device. The main business risk is unmanaged or legacy phones retaining sensitive data or becoming unreliable if users can install untrusted apps. Exposure is likely limited to Huawei P8 and Mate S devices running the listed pre-fix firmware builds. Organizations without mobile asset inventory or with unmanaged BYOD devices may not know whether affected models remain in use. Prioritize this where legacy Huawei phones access business email, files, or messaging. It is not a broad enterprise infrastructure emergency, but unmanaged vulnerable phones can leak data or crash through malicious apps. Mitigation focus: Inventory Huawei P8 and Mate S devices in corporate or BYOD use.; Update affected devices to the listed fixed Huawei builds or later.; Check Huawei PSIRT guidance for model-specific update availability..

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-8682 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 13, 2016, 14: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.