# CVE-2019-2264: Null dereference in Snapdragon Auto, Snapdragon Consumer IOT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables

> A null pointer dereference in the glink channel opening process allows attackers to cause a denial of service on affected Qualcomm 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:** 22 Jul 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-5f5q-pmvm-52cw

## What is CVE-2019-2264?

CVE-2019-2264 is a high-severity vulnerability in Qualcomm Mdm9607 Firmware, published on 22 Jul 2019. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Null pointer dereference occurs for channel context while opening glink channel in Snapdragon Auto, Snapdragon Consumer IOT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables in MDM9607, MDM9640, MSM8909W, QCS405, QCS605, SD 425, SD 427, SD 430, SD 435, SD 439 / SD 429, SD 450, SD 625, SD 632, SD 636, SD 712 / SD 710 / SD 670, SD 820A, SD 835, SD 845 / SD 850, SDM439, SDM630, SDM660, SDX24

Weakness: CWE-476 (NULL Pointer Dereference), CWE-416 (Use After Free)

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

It affects 26 products.


Products: Qualcomm Mdm9607 Firmware, Qualcomm Mdm9640 Firmware, Qualcomm Msm8909w Firmware, Qualcomm Qcs405 Firmware, Qualcomm Qcs605 Firmware, Qualcomm Sd 425 Firmware, Qualcomm Sd 427 Firmware, Qualcomm Sd 429 Firmware, Qualcomm Sd 430 Firmware, Qualcomm Sd 435 Firmware, Qualcomm Sd 439 Firmware, Qualcomm Sd 450 Firmware, Qualcomm Sd 625 Firmware, Qualcomm Sd 632 Firmware, Qualcomm Sd 636 Firmware, Qualcomm Sd 670 Firmware, Qualcomm Sd 710 Firmware, Qualcomm Sd 712 Firmware, Qualcomm Sd 820a Firmware, Qualcomm Sd 835 Firmware and 6 more.

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

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

## Is CVE-2019-2264 being exploited?

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

## Other vulnerabilities in Qualcomm Mdm9607 Firmware

- [CVE-2019-10531](https://insights.sbomify.com/CVE-2019-10531/): Memory corruption in Snapdragon Auto, Snapdragon Mobile, Snapdragon Wearables (critical 9.8)
- [CVE-2019-2276](https://insights.sbomify.com/CVE-2019-2276/): Memory corruption in Snapdragon Auto, Snapdragon Consumer Electronics Connectivity, Snapdragon Consumer IOT, Snapdragon Mobile, Snapdragon Voice & Music (critical 9.8)
- [CVE-2018-5915](https://insights.sbomify.com/CVE-2018-5915/): Denial of service in Snapdragon Automobile, Snapdragon Mobile, Snapdragon Wear (critical 9.8)
- [CVE-2015-9126](https://insights.sbomify.com/CVE-2015-9126/): Memory corruption in Snapdragon Mobile, Snapdragon Wear (critical 9.8)
- [CVE-2016-10479](https://insights.sbomify.com/CVE-2016-10479/): Memory corruption in Snapdragon Mobile (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2019-2264 is a high-severity vulnerability in Qualcomm Mdm9607 Firmware, published on 22 Jul 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-2264 in the wild and no public exploit code.

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

## Sources

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

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