CVE-2015-8681: n/a vulnerability

CVE-2015-8681: The ovisp driver in Huawei P8 smartphones with software GRA-TL00 before GRA-TL00C01B230, GRA-CL00 before GR...

The ovisp 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 allows attackers to cause a denial of service (system crash) or gain privileges via a crafted application with the camera permission, aka an "interface access control vulnerability."

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

Security readout for executives and security teams

Certain Huawei P8 and Mate S smartphone firmware versions exposed a camera-related driver weakness. A malicious app that already has camera permission could crash the phone or gain elevated privileges. This is primarily a legacy mobile fleet risk, not a broad server or cloud exposure. Exposure is limited to Huawei P8 and Mate S devices running the specific pre-fixed firmware builds named in the CVE. Organizations without these legacy devices are unlikely to be affected based on the provided sources. Treat this as a targeted legacy mobile device issue. Prioritize verification if Huawei P8 or Mate S devices remain in use, especially where phones handle sensitive business data or cannot be centrally patched. Mitigation focus: Inventory Huawei P8 and Mate S devices in managed or BYOD fleets.; Update affected devices to the vendor-listed fixed builds or later where available.; Review Huawei PSIRT or carrier firmware guidance for supported update paths..

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