# CVE-2021-1947: Use after free in Snapdragon Compute, Snapdragon Connectivity, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Wearables, Snapdragon Wired Infrastructure and Networking

> A use-after-free in the Qualcomm kernel graphics driver allows attackers to execute arbitrary code or escalate privileges on Snapdragon devices.

- **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:** Yes
- **Published:** 17 Sep 2021
- **Updated:** 3 Aug 2024
- **Also known as:** 2840102, A-187074483, ASB-A-187074483, GHSA-7q63-mgr2-2p5j

## What is CVE-2021-1947?

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

### Official description

Use-after-free vulnerability in kernel graphics driver because of storing an invalid pointer in Snapdragon Compute, Snapdragon Connectivity, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Wearables, Snapdragon Wired Infrastructure and Networking

Weakness: CWE-416 (Use After Free)

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

It affects 87 products.


Products: Qualcomm Apq8009w Firmware, Qualcomm Apq8053 Firmware, Qualcomm Ar9380 Firmware, Qualcomm Ipq8064 Firmware, Qualcomm Ipq8065 Firmware, Qualcomm Ipq8068 Firmware, Qualcomm Ipq8069 Firmware, Qualcomm Msm8909w Firmware, Qualcomm Msm8953 Firmware, Qualcomm Qca6320 Firmware, Qualcomm Qca6390 Firmware, Qualcomm Qca6391 Firmware, Qualcomm Qca6426 Firmware, Qualcomm Qca8337 Firmware, Qualcomm Qca9531 Firmware, Qualcomm Qca9558 Firmware, Qualcomm Qca9561 Firmware, Qualcomm Qca9563 Firmware, Qualcomm Qca9880 Firmware, Qualcomm Qca9882 Firmware and 67 more.

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

Apply the vendor's patch.

## Is CVE-2021-1947 being exploited?

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

## Other vulnerabilities in Qualcomm Apq8009w Firmware

- [CVE-2021-30341](https://insights.sbomify.com/CVE-2021-30341/): Memory corruption in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer Electronics Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Wearables (critical 9.8)
- [CVE-2021-35104](https://insights.sbomify.com/CVE-2021-35104/): Memory corruption in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Voice & Music, Snapdragon Wearables, Snapdragon Wired Infrastructure and Networking (critical 9.8)
- [CVE-2020-11307](https://insights.sbomify.com/CVE-2020-11307/): Memory corruption in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Wearables (critical 9.8)
- [CVE-2021-30342](https://insights.sbomify.com/CVE-2021-30342/): Race condition in Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Voice & Music, Snapdragon Wearables (critical 9.1)
- [CVE-2021-30334](https://insights.sbomify.com/CVE-2021-30334/): Use after free in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Voice & Music, Snapdragon Wearables (high 8.4)

## Fix prompt for AI coding agents

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

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

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

## Sources

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

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