# CVE-2022-22071: Qualcomm Multiple Chipsets Use-After-Free

> A use-after-free vulnerability in Qualcomm Snapdragon firmware allows attackers to execute arbitrary code or escalate privileges via IOCTL calls.

- **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:** Yes, since 5 Dec 2023 (CISA KEV)
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Jun 2022
- **Updated:** 21 Oct 2025
- **Also known as:** GHSA-hx5m-cxr8-37mp

## What is CVE-2022-22071?

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

### Official description

Possible use after free when process shell memory is freed using IOCTL munmap call and process initialization is in progress in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music

Weakness: CWE-416 (Use After Free)

## Which versions are affected by CVE-2022-22071?

It affects 90 products.


Products: Qualcomm Apq8053 Firmware, Qualcomm Ar8031 Firmware, Qualcomm Ar8035 Firmware, Qualcomm Csra6620 Firmware, Qualcomm Csra6640 Firmware, Qualcomm Mdm9150 Firmware, Qualcomm Msm8953 Firmware, Qualcomm Qca6174a Firmware, Qualcomm Qca6390 Firmware, Qualcomm Qca6391 Firmware, Qualcomm Qca6426 Firmware, Qualcomm Qca6436 Firmware, Qualcomm Qca6574 Firmware, Qualcomm Qca6574a Firmware, Qualcomm Qca6574au Firmware, Qualcomm Qca6595au Firmware, Qualcomm Qca6696 Firmware, Qualcomm Qca8081 Firmware, Qualcomm Qca8337 Firmware, Qualcomm Qca9377 Firmware and 70 more.

## How do I fix CVE-2022-22071?

No fix has been published for CVE-2022-22071 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 26 Dec 2023.

## Is CVE-2022-22071 being exploited?

Yes. Attackers have exploited CVE-2022-22071 in the wild since at least 5 Dec 2023.

## Other vulnerabilities in Qualcomm Apq8053 Firmware

- [CVE-2020-11153](https://insights.sbomify.com/CVE-2020-11153/): Memory corruption in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer Electronics Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile (critical 9.8)
- [CVE-2020-3703](https://insights.sbomify.com/CVE-2020-3703/): Memory corruption in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer Electronics Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon IoT, Snapdragon Mobile, Snapdragon Voice & Music (critical 9.8)
- [CVE-2019-14080](https://insights.sbomify.com/CVE-2019-14080/): Memory corruption in Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Wearables (critical 9.8)
- [CVE-2020-3628](https://insights.sbomify.com/CVE-2020-3628/): Information disclosure in Snapdragon Consumer IOT, Snapdragon Mobile (critical 9.8)
- [CVE-2019-14131](https://insights.sbomify.com/CVE-2019-14131/): Memory corruption in Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-22071 and fix it if it is affected.

What it is: CVE-2022-22071 is a high-severity use after free vulnerability in Qualcomm Apq8053 Firmware, published on 14 Jun 2022. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: Yes. Attackers have exploited CVE-2022-22071 in the wild since at least 5 Dec 2023.

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

## Sources

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

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