# CVE-2022-25677: Use after free in Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Wearables, Snapdragon Wired Infrastructure and Networking

> A use-after-free vulnerability in Qualcomm Snapdragon diag allows attackers to execute arbitrary code or escalate privileges via crafted DCI packets.

- **Severity:** Medium 6.7 (`CVSS:3.1/AV:L/AC:L/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:** Yes
- **Published:** 13 Dec 2022
- **Updated:** 22 Apr 2025
- **Also known as:** 3103567, 3122626, A-235114749, GHSA-4gc4-vfjg-7w73, PUB-A-235114749

## What is CVE-2022-25677?

CVE-2022-25677 is a medium-severity use after free vulnerability in Qualcomm Apq8096au Firmware, published on 13 Dec 2022. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Memory corruption in diag due to use after free while processing dci packet in Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Wearables, Snapdragon Wired Infrastructure and Networking

Weakness: CWE-416 (Use After Free)

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

It affects 143 products.


Products: Qualcomm Apq8096au Firmware, Qualcomm Aqt1000 Firmware, Qualcomm Ar9380 Firmware, Qualcomm Csr8811 Firmware, Qualcomm Ipq4018 Firmware, Qualcomm Ipq4019 Firmware, Qualcomm Ipq4028 Firmware, Qualcomm Ipq4029 Firmware, Qualcomm Ipq5010 Firmware, Qualcomm Ipq5018 Firmware, Qualcomm Ipq5028 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, Qualcomm Ipq8070a Firmware and 123 more.

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

Apply the vendor's patch.

## Is CVE-2022-25677 being exploited?

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

## Other vulnerabilities in Qualcomm Apq8096au Firmware

- [CVE-2019-14045](https://insights.sbomify.com/CVE-2019-14045/): Memory corruption in Snapdragon Auto, Snapdragon Consumer IOT, Snapdragon Mobile (critical 9.8)
- [CVE-2017-14911](https://insights.sbomify.com/CVE-2017-14911/): Auth bypass in Snapdragon IoT, Snapdragon Mobile, Snapdragon Automobile (critical 9.8)
- [CVE-2020-11126](https://insights.sbomify.com/CVE-2020-11126/): Memory corruption in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer Electronics Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wired Infrastructure and Networking (critical 9.1)
- [CVE-2022-33243](https://insights.sbomify.com/CVE-2022-33243/): Improper access control in Qualcomm IPC (high 8.4)
- [CVE-2022-22063](https://insights.sbomify.com/CVE-2022-22063/): Memory corruption in Core (high 8.4)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-25677 is a medium-severity use after free vulnerability in Qualcomm Apq8096au Firmware, published on 13 Dec 2022. 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-2022-25677 in the wild and no public exploit code.

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

## Sources

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

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