# CVE-2019-10602: Use after free in Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Wearables

> A use-after-free vulnerability in the display hardware composer allows attackers to execute arbitrary code or escalate privileges on affected Qualcomm Snapdragon devices.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 Jan 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-jfrx-jr32-9rx5

## What is CVE-2019-10602?

CVE-2019-10602 is a high-severity use after free vulnerability in Qualcomm Apq8053 Firmware, published on 21 Jan 2020. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Potential use-after-free heap error during Validate/Present calls on display HW composer in Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Wearables in APQ8053, APQ8096AU, APQ8098, MDM9206, MDM9207C, MDM9607, MDM9650, MSM8909W, MSM8917, MSM8920, MSM8937, MSM8940, MSM8953, MSM8996AU, QCS605, SDA660, SDM845, SDX20, SM8150

Weakness: CWE-416 (Use After Free)

## Which versions are affected by CVE-2019-10602?

It affects 19 products.


Products: Qualcomm Apq8053 Firmware, Qualcomm Apq8096au Firmware, Qualcomm Apq8098 Firmware, Qualcomm Mdm9206 Firmware, Qualcomm Mdm9207c Firmware, Qualcomm Mdm9607 Firmware, Qualcomm Mdm9650 Firmware, Qualcomm Msm8909w Firmware, Qualcomm Msm8917 Firmware, Qualcomm Msm8920 Firmware, Qualcomm Msm8937 Firmware, Qualcomm Msm8940 Firmware, Qualcomm Msm8953 Firmware, Qualcomm Msm8996au Firmware, Qualcomm Qcs605 Firmware, Qualcomm Sda660 Firmware, Qualcomm Sdm845 Firmware, Qualcomm Sdx20 Firmware, Qualcomm Sm8150 Firmware.

## How do I fix CVE-2019-10602?

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

## Is CVE-2019-10602 being exploited?

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

## Other vulnerabilities in Qualcomm Apq8053 Firmware

- [CVE-2022-22071](https://insights.sbomify.com/CVE-2022-22071/): Qualcomm Multiple Chipsets Use-After-Free (high 8.4, exploited in the wild)
- [CVE-2020-11153](https://insights.sbomify.com/CVE-2020-11153/): Memory corruption in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer Electronics Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile (critical 9.8)
- [CVE-2020-3703](https://insights.sbomify.com/CVE-2020-3703/): Memory corruption in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer Electronics Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon IoT, Snapdragon Mobile, Snapdragon Voice & Music (critical 9.8)
- [CVE-2019-14080](https://insights.sbomify.com/CVE-2019-14080/): Memory corruption in Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Wearables (critical 9.8)
- [CVE-2020-3628](https://insights.sbomify.com/CVE-2020-3628/): Information disclosure in Snapdragon Consumer IOT, Snapdragon Mobile (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-10602 and fix it if it is affected.

What it is: CVE-2019-10602 is a high-severity use after free vulnerability in Qualcomm Apq8053 Firmware, published on 21 Jan 2020. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-10602 in the wild and no public exploit code.

Affected product: Qualcomm Apq8053 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-2019-10602/ (Markdown: https://insights.sbomify.com/CVE-2019-10602/index.md)
```

## Sources

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

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