# CVE-2020-11120: Use after free in Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables

> A use-after-free vulnerability in Qualcomm Snapdragon chipsets allows attackers to execute arbitrary code or escalate privileges via a race condition in the event loop.

- **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:** Yes
- **Published:** 8 Sep 2020
- **Updated:** 4 Aug 2024
- **Also known as:** 2556613, A-155652795, ASB-A-155652795, GHSA-mp5p-8378-g7pw

## What is CVE-2020-11120?

CVE-2020-11120 is a high-severity use after free vulnerability in Qualcomm Apq8096au Firmware, published on 8 Sep 2020. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

u'Calling thread may free the data buffer pointer that was passed to the callback and later when event loop executes the callback, data buffer may not be valid and will lead to use after free scenario' in Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables in APQ8096AU, APQ8098, Bitra, Kamorta, MSM8917, MSM8953, MSM8998, QCM2150, QCS405, QCS605, QM215, Rennell, Saipan, SDM429, SDM439, SDM450, SDM632, SM6150, SM7150, SM8150, SM8250, SXR2130

Weakness: CWE-416 (Use After Free)

## Which versions are affected by CVE-2020-11120?

It affects 22 products.


Products: Qualcomm Apq8096au Firmware, Qualcomm Apq8098 Firmware, Qualcomm Bitra Firmware, Qualcomm Kamorta Firmware, Qualcomm Msm8917 Firmware, Qualcomm Msm8953 Firmware, Qualcomm Msm8998 Firmware, Qualcomm Qcm2150 Firmware, Qualcomm Qcs405 Firmware, Qualcomm Qcs605 Firmware, Qualcomm Qm215 Firmware, Qualcomm Rennell Firmware, Qualcomm Saipan Firmware, Qualcomm Sdm429 Firmware, Qualcomm Sdm439 Firmware, Qualcomm Sdm450 Firmware, Qualcomm Sdm632 Firmware, Qualcomm Sm6150 Firmware, Qualcomm Sm7150 Firmware, Qualcomm Sm8150 Firmware and 2 more.

## How do I fix CVE-2020-11120?

Apply the vendor's patch.

## Is CVE-2020-11120 being exploited?

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

## Other vulnerabilities in Qualcomm Apq8096au Firmware

- [CVE-2019-14045](https://insights.sbomify.com/CVE-2019-14045/): Memory corruption in Snapdragon Auto, Snapdragon Consumer IOT, Snapdragon Mobile (critical 9.8)
- [CVE-2017-14911](https://insights.sbomify.com/CVE-2017-14911/): Auth bypass in Snapdragon IoT, Snapdragon Mobile, Snapdragon Automobile (critical 9.8)
- [CVE-2020-11126](https://insights.sbomify.com/CVE-2020-11126/): Memory corruption in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer Electronics Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wired Infrastructure and Networking (critical 9.1)
- [CVE-2022-33243](https://insights.sbomify.com/CVE-2022-33243/): Improper access control in Qualcomm IPC (high 8.4)
- [CVE-2022-22063](https://insights.sbomify.com/CVE-2022-22063/): Memory corruption in Core (high 8.4)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-11120 and fix it if it is affected.

What it is: CVE-2020-11120 is a high-severity use after free vulnerability in Qualcomm Apq8096au Firmware, published on 8 Sep 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-2020-11120 in the wild and no public exploit code.

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

## Sources

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

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