# CVE-2020-11271: Race condition in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables, Snapdragon Wired Infrastructure and Networking

> A race condition in Qualcomm Snapdragon firmware allows out-of-bounds access, potentially enabling code execution or denial of service.

- **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:** 22 Feb 2021
- **Updated:** 4 Aug 2024
- **Also known as:** 2555096, A-172348954, ASB-A-172348954, GHSA-p8mf-qgvp-6754

## What is CVE-2020-11271?

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

### Official description

Possible out of bounds while accessing global control elements due to race condition in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables, Snapdragon Wired Infrastructure and Networking

Weakness: CWE-129 (Improper Validation of Array Index)

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

It affects 340 products.


Products: Qualcomm Aqt1000 Firmware, Qualcomm Ar8031 Firmware, Qualcomm Ar8035 Firmware, Qualcomm Ar9380 Firmware, Qualcomm Csr8811 Firmware, Qualcomm Csra6620 Firmware, Qualcomm Csra6640 Firmware, Qualcomm Fsm10055 Firmware, Qualcomm Fsm10056 Firmware, Qualcomm Ipq4018 Firmware, Qualcomm Ipq4028 Firmware, Qualcomm Ipq4029 Firmware, Qualcomm Ipq6000 Firmware, Qualcomm Ipq6010 Firmware, Qualcomm Ipq6018 Firmware, Qualcomm Ipq6028 Firmware, Qualcomm Ipq8064 Firmware, Qualcomm Ipq8065 Firmware, Qualcomm Ipq8068 Firmware, Qualcomm Ipq8070 Firmware and 320 more.

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

Apply the vendor's patch.

## Is CVE-2020-11271 being exploited?

There is no known exploitation of CVE-2020-11271 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-11271 and fix it if it is affected.

What it is: CVE-2020-11271 is a high-severity vulnerability in Qualcomm Aqt1000 Firmware, published on 22 Feb 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-11271 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-11271/ (Markdown: https://insights.sbomify.com/CVE-2020-11271/index.md)
```

## Sources

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

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