# CVE-2020-11220: Race condition in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Wired Infrastructure and Networking

> A time-of-check to time-of-use race condition in storage SCM commands allows attackers to execute arbitrary 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:** 17 Mar 2021
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-p7xv-94hw-xx6p

## What is CVE-2020-11220?

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

### Official description

While processing storage SCM commands there is a time of check or time of use window where a pointer used could be invalid at a specific time while executing the storage SCM call in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Wired Infrastructure and Networking

Weakness: CWE-367 (Time-of-check Time-of-use (TOCTOU) Race Condition)

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

It affects 131 products.


Products: Qualcomm Aqt1000 Firmware, Qualcomm Ar8035 Firmware, Qualcomm Pm4125 Firmware, Qualcomm Pm4250 Firmware, Qualcomm Pm6125 Firmware, Qualcomm Pm6150 Firmware, Qualcomm Pm6150a Firmware, Qualcomm Pm6150l Firmware, Qualcomm Pm6350 Firmware, Qualcomm Pm640a Firmware, Qualcomm Pm640l Firmware, Qualcomm Pm640p Firmware, Qualcomm Pm7250b Firmware, Qualcomm Pm8004 Firmware, Qualcomm Pm8005 Firmware, Qualcomm Pm8008 Firmware, Qualcomm Pm8350 Firmware, Qualcomm Pm855 Firmware, Qualcomm Pm855a Firmware, Qualcomm Pm855b Firmware and 111 more.

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

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

## Is CVE-2020-11220 being exploited?

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

## Other vulnerabilities in Qualcomm Aqt1000 Firmware

- [CVE-2025-21479](https://insights.sbomify.com/CVE-2025-21479/): Qualcomm Multiple Chipsets Incorrect Authorization (high 8.6, exploited in the wild)
- [CVE-2025-21480](https://insights.sbomify.com/CVE-2025-21480/): Qualcomm Multiple Chipsets Incorrect Authorization (high 8.6, exploited in the wild)
- [CVE-2023-28562](https://insights.sbomify.com/CVE-2023-28562/): Buffer Copy Without Checking Size of Input in QESL (critical 9.8)
- [CVE-2022-40514](https://insights.sbomify.com/CVE-2022-40514/): Buffer copy without checking size of input in WLAN Firmware (critical 9.8)
- [CVE-2022-22096](https://insights.sbomify.com/CVE-2022-22096/): Memory corruption in Snapdragon Connectivity, Snapdragon Mobile (critical 9.8)

## Fix prompt for AI coding agents

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

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

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

## Sources

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

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