# CVE-2021-1900: Use after free in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables

> A race condition in Qualcomm Snapdragon display handling allows attackers to trigger a use-after-free, potentially leading to code execution or privilege escalation.

- **Severity:** High 8.4 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 Jun 2021
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-479q-wh8r-w2j3

## What is CVE-2021-1900?

CVE-2021-1900 is a high-severity use after free vulnerability in Qualcomm Apq8009 Firmware, published on 9 Jun 2021. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Possible use after free in Display due to race condition while creating an external display in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables

Weakness: CWE-416 (Use After Free), CWE-362 (Concurrent Execution using Shared Resource with Improper Synchronization)

## Which versions are affected by CVE-2021-1900?

It affects 90 products.


Products: Qualcomm Apq8009 Firmware, Qualcomm Apq8009w Firmware, Qualcomm Apq8017 Firmware, Qualcomm Apq8053 Firmware, Qualcomm Apq8064au Firmware, Qualcomm Apq8096au Firmware, Qualcomm Aqt1000 Firmware, Qualcomm Ar8031 Firmware, Qualcomm Csra6620 Firmware, Qualcomm Csra6640 Firmware, Qualcomm Mdm9206 Firmware, Qualcomm Mdm9250 Firmware, Qualcomm Mdm9650 Firmware, Qualcomm Msm8909w Firmware, Qualcomm Msm8953 Firmware, Qualcomm Msm8996au Firmware, Qualcomm Qca4020 Firmware, Qualcomm Qca6174a Firmware, Qualcomm Qca6175a Firmware, Qualcomm Qca6310 Firmware and 70 more.

## How do I fix CVE-2021-1900?

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

## Is CVE-2021-1900 being exploited?

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

## Other vulnerabilities in Qualcomm Apq8009 Firmware

- [CVE-2021-1905](https://insights.sbomify.com/CVE-2021-1905/): Qualcomm Multiple Chipsets Use-After-Free (high 8.4, exploited in the wild)
- [CVE-2020-11261](https://insights.sbomify.com/CVE-2020-11261/): Qualcomm Multiple Chipsets Improper Input Validation (high 7.8, exploited in the wild)
- [CVE-2021-1906](https://insights.sbomify.com/CVE-2021-1906/): Qualcomm Multiple Chipsets Detection of Error Condition Without Action (medium 6.2, exploited in the wild)
- [CVE-2022-40510](https://insights.sbomify.com/CVE-2022-40510/): Buffer copy without checking size of input in Audio. (critical 9.8)
- [CVE-2022-22088](https://insights.sbomify.com/CVE-2022-22088/): Integer Overflow to Buffer Overflow in Bluetooth HOST (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-1900 and fix it if it is affected.

What it is: CVE-2021-1900 is a high-severity use after free vulnerability in Qualcomm Apq8009 Firmware, published on 9 Jun 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-2021-1900 in the wild and no public exploit code.

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

## Sources

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

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