# CVE-2022-25702: Denial of service in Snapdragon Auto, Snapdragon Compute, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Wearables

> A reachable assertion in the modem allows attackers to cause a denial of service via reconfiguration messages on Qualcomm Snapdragon devices.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 Dec 2022
- **Updated:** 22 Apr 2025
- **Also known as:** GHSA-6r5j-6vgv-h834

## What is CVE-2022-25702?

CVE-2022-25702 is a high-severity denial of service vulnerability in Qualcomm Apq8009 Firmware, published on 13 Dec 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Denial of service in modem due to reachable assertion while processing reconfiguration message in Snapdragon Auto, Snapdragon Compute, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Wearables

Weakness: CWE-617 (Reachable Assertion)

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

It affects 79 products.


Products: Qualcomm Apq8009 Firmware, Qualcomm Apq8017 Firmware, Qualcomm Apq8037 Firmware, Qualcomm Aqt1000 Firmware, Qualcomm Ar8035 Firmware, Qualcomm Fsm10055 Firmware, Qualcomm Msm8108 Firmware, Qualcomm Msm8208 Firmware, Qualcomm Msm8209 Firmware, Qualcomm Msm8608 Firmware, Qualcomm Msm8917 Firmware, Qualcomm Msm8937 Firmware, Qualcomm Qca6390 Firmware, Qualcomm Qca6391 Firmware, Qualcomm Qca6421 Firmware, Qualcomm Qca6426 Firmware, Qualcomm Qca6431 Firmware, Qualcomm Qca6436 Firmware, Qualcomm Qca8081 Firmware, Qualcomm Qca8337 Firmware and 59 more.

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

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

## Is CVE-2022-25702 being exploited?

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

What it is: CVE-2022-25702 is a high-severity denial of service vulnerability in Qualcomm Apq8009 Firmware, published on 13 Dec 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-25702 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-2022-25702/ (Markdown: https://insights.sbomify.com/CVE-2022-25702/index.md)
```

## Sources

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

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