# CVE-2019-10565: Use after free in Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer Electronics Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables

> A double free vulnerability in Qualcomm Snapdragon sensor power settings allows attackers to cause denial of service or execute arbitrary code via race conditions.

- **Severity:** Critical 9.8 (`CVSS:3.1/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:** 6 Nov 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-774x-p4vv-cf8c

## What is CVE-2019-10565?

CVE-2019-10565 is a critical use after free vulnerability in Qualcomm Apq8053 Firmware, published on 6 Nov 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Double free issue can happen when sensor power settings is freed by some thread while another thread try to access. in Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer Electronics Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables in APQ8053, MDM9206, MDM9207C, MDM9607, MSM8905, MSM8909, MSM8909W, QCN7605, QCS405, QCS605, SDM845, SDX24, SXR1130

Weakness: CWE-415 (Double Free)

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

It affects 13 products.


Products: Qualcomm Apq8053 Firmware, Qualcomm Mdm9206 Firmware, Qualcomm Mdm9207c Firmware, Qualcomm Mdm9607 Firmware, Qualcomm Msm8905 Firmware, Qualcomm Msm8909 Firmware, Qualcomm Msm8909w Firmware, Qualcomm Qcn7605 Firmware, Qualcomm Qcs405 Firmware, Qualcomm Qcs605 Firmware, Qualcomm Sdm845 Firmware, Qualcomm Sdx24 Firmware, Qualcomm Sxr1130 Firmware.

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

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

## Is CVE-2019-10565 being exploited?

There is no known exploitation of CVE-2019-10565 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-10565 and fix it if it is affected.

What it is: CVE-2019-10565 is a critical use after free vulnerability in Qualcomm Apq8053 Firmware, published on 6 Nov 2019. 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-2019-10565 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-10565/ (Markdown: https://insights.sbomify.com/CVE-2019-10565/index.md)
```

## Sources

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

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