# CVE-2020-11152: Race condition in Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables

> A race condition in the HAL layer allows attackers to potentially execute code or escalate privileges on Qualcomm Snapdragon devices.

- **Severity:** Medium 6.4 (`CVSS:3.1/AV:L/AC:H/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-2ff2-j84c-3hw4

## What is CVE-2020-11152?

CVE-2020-11152 is a medium-severity vulnerability in Qualcomm, Inc. Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music, 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

Race condition in HAL layer while processing callback objects received from HIDL due to lack of synchronization between accessing objects in Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables

Weakness: CWE-362 (Concurrent Execution using Shared Resource with Improper Synchronization)

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

It affects 160 products.


Products: Qualcomm Apq8009w, Qualcomm Apq8017, Qualcomm Apq8037, Qualcomm Apq8052, Qualcomm Apq8053, Qualcomm Apq8056, Qualcomm Apq8076, Qualcomm Apq8096au, Qualcomm Aqt1000, Qualcomm Ar8031, Qualcomm Csra6620, Qualcomm Csra6640, Qualcomm Msm8909w, Qualcomm Msm8916, Qualcomm Msm8917, Qualcomm Msm8920, Qualcomm Msm8937, Qualcomm Msm8940, Qualcomm Msm8952, Qualcomm Msm8953 and 140 more.

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

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

## Is CVE-2020-11152 being exploited?

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

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

- [CVE-2020-11167](https://insights.sbomify.com/CVE-2020-11167/): Memory corruption in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2020-11152 is a medium-severity vulnerability in Qualcomm, Inc. Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music, 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-11152 in the wild and no public exploit code.

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

## Sources

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

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