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

> A memory corruption vulnerability in Qualcomm Snapdragon bootchain allows attackers to corrupt Linux kernel memory, 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:** 16 Sep 2024
- **Also known as:** GHSA-cm44-x78v-rrf8

## What is CVE-2016-10458?

CVE-2016-10458 is a critical memory corruption vulnerability in Qualcomm Sd 205 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 SD 210/SD 212/SD 205, SD 410/12, SD 425, SD 427, SD 430, SD 435, SD 450, SD 615/16/SD 415, SD 617, SD 625, SD 650/52, SD 808, SD 810, SD 820, SD 835, SD 845, SDM630, SDM636, SDM660, SDX20, and Snapdragon_High_Med_2016, the 'proper' solution for this will be to ensure that any users of qsee_log in the bootchain (before Linux boots) unallocate their buffers and clear the qsee_log pointer. Until support for that is implemented in TZ and the bootloader, enable tz_log to avoid potential scribbling. This solution will prevent the linux kernel memory corruption.

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

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

It affects 25 products.


Products: Qualcomm Sd 205 Firmware, Qualcomm Sd 210 Firmware, Qualcomm Sd 212 Firmware, Qualcomm Sd 410 Firmware, Qualcomm Sd 412 Firmware, Qualcomm Sd 415 Firmware, Qualcomm Sd 425 Firmware, Qualcomm Sd 427 Firmware, Qualcomm Sd 430 Firmware, Qualcomm Sd 450 Firmware, Qualcomm Sd 615 Firmware, Qualcomm Sd 616 Firmware, Qualcomm Sd 617 Firmware, Qualcomm Sd 625 Firmware, Qualcomm Sd 650 Firmware, Qualcomm Sd 652 Firmware, Qualcomm Sd 808 Firmware, Qualcomm Sd 810 Firmware, Qualcomm Sd 820 Firmware, Qualcomm Sd 835 Firmware and 5 more.

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

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

## Is CVE-2016-10458 being exploited?

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

## Other vulnerabilities in Qualcomm Sd 205 Firmware

- [CVE-2014-10056](https://insights.sbomify.com/CVE-2014-10056/): Memory corruption in Snapdragon Mobile (critical 9.8)
- [CVE-2015-9205](https://insights.sbomify.com/CVE-2015-9205/): Memory corruption in Snapdragon Mobile, Snapdragon Wear (critical 9.8)
- [CVE-2016-10407](https://insights.sbomify.com/CVE-2016-10407/): Integer overflow in Snapdragon Mobile (critical 9.8)
- [CVE-2016-10467](https://insights.sbomify.com/CVE-2016-10467/): Weak cryptography in Snapdragon Automobile, Snapdragon Mobile (critical 9.8)
- [CVE-2016-10475](https://insights.sbomify.com/CVE-2016-10475/): Integer overflow in Snapdragon Mobile (critical 9.8)

## Fix prompt for AI coding agents

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

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

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

## Sources

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

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