# CVE-2022-22063: Memory corruption in Core

> Memory corruption in Qualcomm Snapdragon boot remapper allows attackers to execute arbitrary code or escalate privileges.

- **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:** No
- **Published:** 14 Dec 2022
- **Updated:** 18 Apr 2025
- **Also known as:** GHSA-3vr9-mjrf-j2pc

## What is CVE-2022-22063?

CVE-2022-22063 is a high-severity memory corruption vulnerability in Qualcomm Apq8096au Firmware, published on 14 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 Core due to improper configuration in boot remapper.

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

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

It affects 8 products.


Products: Qualcomm Apq8096au Firmware, Qualcomm Mdm9640 Firmware, Qualcomm Mdm9645 Firmware, Qualcomm Qca6174 Firmware, Qualcomm Qca6174a Firmware, Qualcomm Qca6574a Firmware, Qualcomm Qca6574au Firmware, Qualcomm Wcn3990 Firmware.

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

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

## Is CVE-2022-22063 being exploited?

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

Public exploit code:

- Security issue in the hypervisor firmware of some older Qualcomm chipsets (github_poc): https://github.com/msm8916-mainline/CVE-2022-22063

## 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-22098](https://insights.sbomify.com/CVE-2022-22098/): Memory corruption in Snapdragon Auto (high 8.4)

## Fix prompt for AI coding agents

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

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

## Sources

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

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