# CVE-2016-10419: Memory corruption in Snapdragon Mobile

> Out-of-bounds access in Qualcomm Snapdragon scheduler allows attackers to potentially execute code or escalate privileges via uninitialized object numbers.

- **Severity:** Critical 9.8 (`CVSS:3.0/AV:N/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:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Apr 2018
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-rvh7-m625-vrxv

## What is CVE-2016-10419?

CVE-2016-10419 is a critical memory corruption vulnerability in Qualcomm Mdm9640 Firmware, published on 18 Apr 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

In Android before 2018-04-05 or earlier security patch level on Qualcomm Snapdragon Mobile MDM9640, MDM9645, MDM9650, MDM9655, SD 450, SD 625, SD 650/52, SD 820, SD 835, SD 845, SD 850, and SDX20, when initializing scheduler object service request, an out of bounds access could occur due to uninitialized object number.

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

## Which versions are affected by CVE-2016-10419?

It affects 13 products.


Products: Qualcomm Mdm9640 Firmware, Qualcomm Mdm9645 Firmware, Qualcomm Mdm9650 Firmware, Qualcomm Mdm9655 Firmware, Qualcomm Sd 450 Firmware, Qualcomm Sd 625 Firmware, Qualcomm Sd 650 Firmware, Qualcomm Sd 652 Firmware, Qualcomm Sd 820 Firmware, Qualcomm Sd 835 Firmware, Qualcomm Sd 845 Firmware, Qualcomm Sd 850 Firmware, Qualcomm Sdx20 Firmware.

## How do I fix CVE-2016-10419?

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

## Is CVE-2016-10419 being exploited?

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

## Other vulnerabilities in Qualcomm Mdm9640 Firmware

- [CVE-2016-10442](https://insights.sbomify.com/CVE-2016-10442/): Privilege escalation in Snapdragon Mobile (critical 9.8)
- [CVE-2016-10486](https://insights.sbomify.com/CVE-2016-10486/): Memory corruption in Snapdragon Automobile, Snapdragon Mobile (critical 9.8)
- [CVE-2017-18137](https://insights.sbomify.com/CVE-2017-18137/): Memory corruption in Snapdragon Mobile (critical 9.8)
- [CVE-2019-2316](https://insights.sbomify.com/CVE-2019-2316/): Use after free in Snapdragon Auto, Snapdragon Consumer IOT, Snapdragon Mobile, Snapdragon Voice & Music (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2016-10419 and fix it if it is affected.

What it is: CVE-2016-10419 is a critical memory corruption vulnerability in Qualcomm Mdm9640 Firmware, published on 18 Apr 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2016-10419 in the wild and no public exploit code.

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

## Sources

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

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