# CVE-2022-40516: Stack-based buffer overflow in Core

> A stack-based buffer overflow in Qualcomm Snapdragon Core 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:** 6 Jan 2023
- **Updated:** 9 Apr 2025
- **Also known as:** GHSA-42pq-h6rj-6c6q

## What is CVE-2022-40516?

CVE-2022-40516 is a high-severity memory corruption vulnerability in Qualcomm Aqt1000 Firmware, published on 6 Jan 2023. 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 stack-based buffer overflow.

Weakness: CWE-787 (Out-of-bounds Write), CWE-121 (Stack-based Buffer Overflow)

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

It affects 184 products.


Products: Qualcomm Aqt1000 Firmware, Qualcomm Ar8031 Firmware, Qualcomm Ar8035 Firmware, Qualcomm Csr8811 Firmware, Qualcomm Csra6620 Firmware, Qualcomm Csra6640 Firmware, Qualcomm Csrb31024 Firmware, Qualcomm Fsm10056 Firmware, Qualcomm Ipq6000 Firmware, Qualcomm Ipq6005 Firmware, Qualcomm Ipq6010 Firmware, Qualcomm Ipq6018 Firmware, Qualcomm Ipq6028 Firmware, Qualcomm Ipq9008 Firmware, Qualcomm Ipq9574 Firmware, Qualcomm Mdm9150 Firmware, Qualcomm Mdm9205 Firmware, Qualcomm Qam8295p Firmware, Qualcomm Qca4004 Firmware, Qualcomm Qca4024 Firmware and 164 more.

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

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

## Is CVE-2022-40516 being exploited?

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

## Other vulnerabilities in Qualcomm Aqt1000 Firmware

- [CVE-2025-21479](https://insights.sbomify.com/CVE-2025-21479/): Qualcomm Multiple Chipsets Incorrect Authorization (high 8.6, exploited in the wild)
- [CVE-2025-21480](https://insights.sbomify.com/CVE-2025-21480/): Qualcomm Multiple Chipsets Incorrect Authorization (high 8.6, exploited in the wild)
- [CVE-2023-28562](https://insights.sbomify.com/CVE-2023-28562/): Buffer Copy Without Checking Size of Input in QESL (critical 9.8)
- [CVE-2022-40514](https://insights.sbomify.com/CVE-2022-40514/): Buffer copy without checking size of input in WLAN Firmware (critical 9.8)
- [CVE-2022-22096](https://insights.sbomify.com/CVE-2022-22096/): Memory corruption in Snapdragon Connectivity, Snapdragon Mobile (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-40516 is a high-severity memory corruption vulnerability in Qualcomm Aqt1000 Firmware, published on 6 Jan 2023. 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-40516 in the wild and no public exploit code.

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

## Sources

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

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