CVEs-PoC/2016/CVE-2016-10458.md

### [CVE-2016-10458](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-10458)
![](https://img.shields.io/static/v1?label=Product&message=Snapdragon%20Mobile&color=blue)
![](https://img.shields.io/static/v1?label=Version&message=SD%20210%2FSD%20212%2FSD%20205%2C%20SD%20410%2F12%2C%20SD%20425%2C%20SD%20427%2C%20SD%20430%2C%20SD%20435%2C%20SD%20450%2C%20SD%20615%2F16%2FSD%20415%2C%20SD%20617%2C%20SD%20625%2C%20SD%20650%2F52%2C%20SD%20808%2C%20SD%20810%2C%20SD%20820%2C%20SD%20835%2C%20SD%20845%2C%20SDM630%2C%20SDM636%2C%20SDM660%2C%20SDX20%2C%20Snapdragon_High_Med_2016%20&color=brightgreen)
![](https://img.shields.io/static/v1?label=Vulnerability&message=Use%20of%20Uninitialized%20Variable%20in%20Core.&color=brightgreen)

### 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.

### POC

#### Reference
- http://www.securityfocus.com/bid/103671

#### Github
No PoCs found on GitHub currently.