# CVE-2017-15316: Use after free in Mate 9

> A malicious application can trigger a double free in the GPU driver, leading to system crashes or arbitrary code execution on Huawei Mate 9 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:** 22 Dec 2017
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-r9g8-36p4-9ggj

## What is CVE-2017-15316?

CVE-2017-15316 is a high-severity use after free vulnerability in Huawei Technologies Co., Ltd. Mate 9, published on 22 Dec 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 of Mate 9 Huawei smart phones with software before MHA-AL00B 8.0.0.334(C00) and Mate 9 Pro Huawei smart phones with software before LON-AL00B 8.0.0.334(C00) has a memory double free vulnerability. An attacker tricks a user into installing a malicious application, and the application can call special API, which triggers double free and causes a system crash or arbitrary code execution.

Weakness: CWE-415 (Double Free)

## Which versions are affected by CVE-2017-15316?

It affects 2 products.


Products: Huawei Mate 9 Firmware, Huawei Mate 9 Pro Firmware.

## How do I fix CVE-2017-15316?

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

## Is CVE-2017-15316 being exploited?

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

## Other vulnerabilities in Huawei Technologies Co., Ltd. Mate 9

- [CVE-2017-2716](https://insights.sbomify.com/CVE-2017-2716/): Memory corruption in Mate 9 (high 7.8)
- [CVE-2017-8142](https://insights.sbomify.com/CVE-2017-8142/): Use after free in Mate 9, Mate 9 Pro (high 7.8)
- [CVE-2017-2706](https://insights.sbomify.com/CVE-2017-2706/): Path traversal in Mate 9 (high 7.1)
- [CVE-2017-2707](https://insights.sbomify.com/CVE-2017-2707/): Privilege escalation in Mate 9 (high 7.1)
- [CVE-2017-2702](https://insights.sbomify.com/CVE-2017-2702/): Auth bypass in Mate 9 (medium 6.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-15316 and fix it if it is affected.

What it is: CVE-2017-15316 is a high-severity use after free vulnerability in Huawei Technologies Co., Ltd. Mate 9, published on 22 Dec 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-2017-15316 in the wild and no public exploit code.

Affected product: Huawei Technologies Co., Ltd. Mate 9. 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-2017-15316/ (Markdown: https://insights.sbomify.com/CVE-2017-15316/index.md)
```

## Sources

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

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