# CVE-2022-25654: Memory corruption in Snapdragon Auto, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Wearables

> Memory corruption in the Qualcomm Snapdragon kernel allows attackers to execute arbitrary code or escalate privileges via improper input validation in ION commands.

- **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:** 16 Sep 2022
- **Updated:** 3 Aug 2024
- **Also known as:** 3075470, A-223230190, GHSA-6wxq-8rgv-3c23, PUB-A-223230190

## What is CVE-2022-25654?

CVE-2022-25654 is a medium-severity memory corruption vulnerability in Qualcomm Apq8096au Firmware, published on 16 Sep 2022. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Memory corruption in kernel due to improper input validation while processing ION commands in Snapdragon Auto, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Wearables

Weakness: CWE-787 (Out-of-bounds Write)

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

It affects 21 products.


Products: Qualcomm Apq8096au Firmware, Qualcomm Mdm9650 Firmware, Qualcomm Qca6174a Firmware, Qualcomm Qca6574au Firmware, Qualcomm Qcs603 Firmware, Qualcomm Qcs605 Firmware, Qualcomm Qualcomm215 Firmware, Qualcomm Sd429 Firmware, Qualcomm Sd820 Firmware, Qualcomm Sdm429w Firmware, Qualcomm Wcd9326 Firmware, Qualcomm Wcd9335 Firmware, Qualcomm Wcd9341 Firmware, Qualcomm Wcn3615 Firmware, Qualcomm Wcn3620 Firmware, Qualcomm Wcn3660b Firmware, Qualcomm Wcn3680 Firmware, Qualcomm Wcn3980 Firmware, Qualcomm Wcn3990 Firmware, Qualcomm Wsa8810 Firmware and 1 more.

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

Apply the vendor's patch.

## Is CVE-2022-25654 being exploited?

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

What it is: CVE-2022-25654 is a medium-severity memory corruption vulnerability in Qualcomm Apq8096au Firmware, published on 16 Sep 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-25654 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-25654/ (Markdown: https://insights.sbomify.com/CVE-2022-25654/index.md)
```

## Sources

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

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