# CVE-2017-14915: Use after free in Snapdragon Mobile

> A use-after-free vulnerability in Qualcomm Snapdragon Mobile firmware allows attackers to execute arbitrary code or escalate privileges via compromised client structures.

- **Severity:** Critical 9.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 30 Mar 2018
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-3m53-3rwg-2453

## What is CVE-2017-14915?

CVE-2017-14915 is a critical use after free vulnerability in Qualcomm Sd 625 Firmware, published on 30 Mar 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

In Android before 2018-01-05 on Qualcomm Snapdragon Mobile SD 625, SD 650/52, SD 835, accessing SPCOM functions with a compromised client structure can result in a Use After Free condition.

Weakness: CWE-416 (Use After Free)

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

It affects 4 products.


Products: Qualcomm Sd 625 Firmware, Qualcomm Sd 650 Firmware, Qualcomm Sd 652 Firmware, Qualcomm Sd 835 Firmware.

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

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

## Is CVE-2017-14915 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2017-14915 is a critical use after free vulnerability in Qualcomm Sd 625 Firmware, published on 30 Mar 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2017-14915 in the wild and no public exploit code.

Affected product: Qualcomm Sd 625 Firmware. 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-14915/ (Markdown: https://insights.sbomify.com/CVE-2017-14915/index.md)
```

## Sources

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

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