# CVE-2019-2250: Memory corruption in Snapdragon Compute, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile

> A kernel vulnerability allows attackers to write to arbitrary memory addresses during thread operations, potentially enabling code execution or privilege escalation on Snapdragon devices.

- **Severity:** High 7.8 (`CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 24 May 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-h248-f9g9-r4hw

## What is CVE-2019-2250?

CVE-2019-2250 is a high-severity memory corruption vulnerability in Qualcomm Qcs605 Firmware, published on 24 May 2019. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Kernel can write to arbitrary memory address passed by user while freeing/stopping a thread in Snapdragon Compute, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile in QCS605, SD 675, SD 712 / SD 710 / SD 670, SD 835, SD 845 / SD 850, SD 855, SD 8CX, SM7150, SXR1130

Weakness: CWE-20 (Improper Input Validation), CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

## Which versions are affected by CVE-2019-2250?

It affects 12 products.


Products: Qualcomm Qcs605 Firmware, Qualcomm Sd 670 Firmware, Qualcomm Sd 675 Firmware, Qualcomm Sd 710 Firmware, Qualcomm Sd 712 Firmware, Qualcomm Sd 835 Firmware, Qualcomm Sd 845 Firmware, Qualcomm Sd 850 Firmware, Qualcomm Sd 855 Firmware, Qualcomm Sd 8cx Firmware, Qualcomm Sm7150 Firmware, Qualcomm Sxr1130 Firmware.

## How do I fix CVE-2019-2250?

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

## Is CVE-2019-2250 being exploited?

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

## Other vulnerabilities in Qualcomm Qcs605 Firmware

- [CVE-2019-14132](https://insights.sbomify.com/CVE-2019-14132/): Memory corruption in Snapdragon Auto, Snapdragon Consumer IOT, Snapdragon Mobile (critical 9.8)
- [CVE-2019-14044](https://insights.sbomify.com/CVE-2019-14044/): Memory corruption in Snapdragon Consumer IOT, Snapdragon Mobile (high 7.8)
- [CVE-2019-14046](https://insights.sbomify.com/CVE-2019-14046/): Memory corruption in Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer Electronics Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music (high 7.8)
- [CVE-2019-10545](https://insights.sbomify.com/CVE-2019-10545/): Null dereference in Snapdragon Auto, Snapdragon Consumer Electronics Connectivity, Snapdragon Consumer IOT, Snapdragon Mobile, Snapdragon Voice & Music (medium 5.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-2250 and fix it if it is affected.

What it is: CVE-2019-2250 is a high-severity memory corruption vulnerability in Qualcomm Qcs605 Firmware, published on 24 May 2019. 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-2019-2250 in the wild and no public exploit code.

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

## Sources

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

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