# CVE-2016-10436: Memory corruption in Small Cell SoC , Snapdragon Mobile, Snapdragon Wear

> Improper input validation in Qualcomm Snapdragon SoCs allows attackers to cause memory corruption, potentially leading to code execution or privilege escalation.

- **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-p6h5-47pm-j65h

## What is CVE-2016-10436?

CVE-2016-10436 is a critical memory corruption vulnerability in Qualcomm Ipq4019 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 Small Cell SoC, Snapdragon Mobile, and Snapdragon Wear FSM9055, IPQ4019, IPQ8064, MDM9206, MDM9607, MDM9635M, MDM9640, MDM9650, MSM8909W, QCA4531, QCA9980, SD 210/SD 212/SD 205, SD 400, SD 410/12, SD 425, SD 430, SD 450, SD 615/16/SD 415, SD 617, SD 625, SD 650/52, SD 808, SD 810, SD 820, SD 835, and SDX20, improper input validation infuse read request leads to memory corruption.

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

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

It affects 33 products.


Products: Qualcomm Fsm9055 Firmware, Qualcomm Ipq4019 Firmware, Qualcomm Ipq8064 Firmware, Qualcomm Mdm9206 Firmware, Qualcomm Mdm9607 Firmware, Qualcomm Mdm9635m Firmware, Qualcomm Mdm9640 Firmware, Qualcomm Mdm9645 Firmware, Qualcomm Mdm9650 Firmware, Qualcomm Msm8909w Firmware, Qualcomm Qca4531 Firmware, Qualcomm Qca9980 Firmware, Qualcomm Sd 205 Firmware, Qualcomm Sd 210 Firmware, Qualcomm Sd 212 Firmware, Qualcomm Sd 400 Firmware, Qualcomm Sd 410 Firmware, Qualcomm Sd 412 Firmware, Qualcomm Sd 415 Firmware, Qualcomm Sd 425 Firmware and 13 more.

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

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

## Is CVE-2016-10436 being exploited?

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

## Other vulnerabilities in Qualcomm Ipq4019 Firmware

- [CVE-2014-10052](https://insights.sbomify.com/CVE-2014-10052/): Information disclosure in Snapdragon Mobile, Snapdragon Wear, Small Cell SoC (critical 9.8)
- [CVE-2015-9138](https://insights.sbomify.com/CVE-2015-9138/): Memory corruption in Snapdragon Automobile, Snapdragon Mobile, Snapdragon Wear, Small Cell SoC (critical 9.8)
- [CVE-2015-9196](https://insights.sbomify.com/CVE-2015-9196/): Privilege escalation in Snapdragon Mobile, Small Cell SoC (critical 9.8)
- [CVE-2015-9224](https://insights.sbomify.com/CVE-2015-9224/): Memory corruption in Snapdragon Automobile, Snapdragon Mobile, Snapdragon Wear, Small Cell SoC (critical 9.8)
- [CVE-2016-10412](https://insights.sbomify.com/CVE-2016-10412/): Integer overflow in Small Cell SoC , Snapdragon Mobile, Snapdragon Wear (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2016-10436 is a critical memory corruption vulnerability in Qualcomm Ipq4019 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-10436 in the wild and no public exploit code.

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

## Sources

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

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