# CVE-2020-11148: Use after free in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Wearables

> A use-after-free vulnerability in Qualcomm Snapdragon HIDL allows attackers to execute arbitrary code or escalate privileges via race conditions.

- **Severity:** Medium 6.7 (`CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 Jan 2021
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-3wqp-fp8q-5rmq

## What is CVE-2020-11148?

CVE-2020-11148 is a medium-severity use after free vulnerability in Qualcomm, Inc. Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Wearables, published on 21 Jan 2021. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Use after free issue in HIDL while using callback to post event in Rx thread when internal mutex is not acquired and meantime close is triggered and callback instance is deleted in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Wearables

Weakness: CWE-416 (Use After Free)

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

It affects 246 products.


Products: Qualcomm Apq8017, Qualcomm Apq8053, Qualcomm Msm8917, Qualcomm Msm8953, Qualcomm Pm215, Qualcomm Pm3003a, Qualcomm Pm439, Qualcomm Pm6125, Qualcomm Pm6150, Qualcomm Pm6150a, Qualcomm Pm6150l, Qualcomm Pm6350, Qualcomm Pm640a, Qualcomm Pm640l, Qualcomm Pm640p, Qualcomm Pm660, Qualcomm Pm660l, Qualcomm Pm670, Qualcomm Pm670l, Qualcomm Pm7150a and 226 more.

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

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

## Is CVE-2020-11148 being exploited?

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

## Other vulnerabilities in Qualcomm, Inc. Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Wearables

- [CVE-2020-11140](https://insights.sbomify.com/CVE-2020-11140/): Memory corruption in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon IoT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables, Snapdragon Wired Infrastructure and Networking (critical 9.8)
- [CVE-2020-11139](https://insights.sbomify.com/CVE-2020-11139/): Memory corruption in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon IoT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables, Snapdragon Wired Infrastructure and Networking (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2020-11148 is a medium-severity use after free vulnerability in Qualcomm, Inc. Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Wearables, published on 21 Jan 2021. 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-11148 in the wild and no public exploit code.

Affected product: Qualcomm, Inc. Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Wearables. 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-11148/ (Markdown: https://insights.sbomify.com/CVE-2020-11148/index.md)
```

## Sources

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

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