# CVE-2015-8089: Privilege escalation in n/a

> Local attackers can read or write arbitrary kernel memory via a crafted app, leading to privilege escalation or system crashes on Huawei P7 devices.

- **Severity:** High 7.8 (`CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 23 May 2017
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-pw9x-rmc8-c7w8

## What is CVE-2015-8089?

CVE-2015-8089 is a high-severity vulnerability in n/a, published on 23 May 2017. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

The GPU driver in Huawei P7 phones with software P7-L00 before P7-L00C17B851, P7-L05 before P7-L05C00B851, and P7-L09 before P7-L09C92B851 allows local users to read or write to arbitrary kernel memory locations and consequently cause a denial of service (system crash) or gain privileges via a crafted application.

Weakness: CWE-264

## Which versions are affected by CVE-2015-8089?

It affects 3 products.


Products: Huawei P7-L00 Firmware, Huawei P7-L05 Firmware, Huawei P7-L09 Firmware.

## How do I fix CVE-2015-8089?

No fix has been published for CVE-2015-8089 yet. Limit exposure of the affected software until one is available.

## Is CVE-2015-8089 being exploited?

There is no known exploitation of CVE-2015-8089 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2015-8089 and fix it if it is affected.

What it is: CVE-2015-8089 is a high-severity vulnerability in n/a, published on 23 May 2017. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2015-8089 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2015-8089/ (Markdown: https://insights.sbomify.com/CVE-2015-8089/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2015-8089
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2015-8089
- OSV: https://osv.dev/vulnerability/CVE-2015-8089

---
From sbomify Insights: https://insights.sbomify.com/CVE-2015-8089/
Summaries are generated and may contain mistakes; the official description above is the record.