# CVE-2020-11231: Race condition in Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile

> Concurrent thread execution causes pointer corruption and heap corruption in Qualcomm Snapdragon components, potentially allowing code execution or privilege escalation.

- **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:** Yes
- **Published:** 7 Apr 2021
- **Updated:** 4 Aug 2024
- **Also known as:** 2713479, A-170141832, GHSA-ccm8-j9m5-h2cw, PUB-A-170141832

## What is CVE-2020-11231?

CVE-2020-11231 is a medium-severity vulnerability in Qualcomm Apq8017 Firmware, published on 7 Apr 2021. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Two threads call one or both functions concurrently leading to corruption of pointers and reference counters which in turn can lead to heap corruption in Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile

Weakness: CWE-415 (Double Free)

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

It affects 215 products.


Products: Qualcomm Apq8017 Firmware, Qualcomm Apq8053 Firmware, Qualcomm Aqt1000 Firmware, Qualcomm Msm8917 Firmware, Qualcomm Msm8953 Firmware, Qualcomm Pm215 Firmware, Qualcomm Pm3003a Firmware, Qualcomm Pm439 Firmware, Qualcomm Pm6125 Firmware, Qualcomm Pm6150 Firmware, Qualcomm Pm6150l Firmware, Qualcomm Pm7150a Firmware, Qualcomm Pm7150l Firmware, Qualcomm Pm7250 Firmware, Qualcomm Pm7250b Firmware, Qualcomm Pm7350c Firmware, Qualcomm Pm8008 Firmware, Qualcomm Pm8009 Firmware, Qualcomm Pm8150a Firmware, Qualcomm Pm8150b Firmware and 195 more.

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

Apply the vendor's patch.

## Is CVE-2020-11231 being exploited?

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

## Other vulnerabilities in Qualcomm Apq8017 Firmware

- [CVE-2025-21483](https://insights.sbomify.com/CVE-2025-21483/): Improper Restriction of Operations within the Bounds of a Memory Buffer in Data Network Stack & Connectivity (critical 9.8)
- [CVE-2021-1933](https://insights.sbomify.com/CVE-2021-1933/): Denial of service in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Wearables (critical 9.8)
- [CVE-2021-1946](https://insights.sbomify.com/CVE-2021-1946/): Null dereference in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile (critical 9.8)
- [CVE-2020-11176](https://insights.sbomify.com/CVE-2020-11176/): Memory corruption in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon IoT, Snapdragon Mobile (critical 9.8)
- [CVE-2020-11291](https://insights.sbomify.com/CVE-2020-11291/): Memory corruption in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon IoT, Snapdragon Mobile (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2020-11231 is a medium-severity vulnerability in Qualcomm Apq8017 Firmware, published on 7 Apr 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-11231 in the wild and no public exploit code.

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

## Sources

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

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