CVE-2015-9208

CVE-2015-9208 affects Android on Qualcomm Snapdragon devices (various SoCs listed). The vulnerability arises because tzbsp_pil_verify_sig() does not strictly constrain the ELF/program headers and hash segment pointers to secure memory; it only ensures addresses are not in non-secure memory, allow...

CVE-2016-10491

In Android before 2018-04-05 or earlier security patch level on Qualcomm Snapdragon Mobile and Snapdragon Wear MDM9206, MDM9607, MDM9625, MDM9635M, MDM9640, MDM9645, MDM9650, MDM9655, MSM8909W, 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...

CVE-2015-9193

In Android before 2018-04-05 or earlier security patch level on Qualcomm Snapdragon Automobile, Snapdragon Mobile, and Snapdragon Wear MDM9206, MDM9650, MSM8909W, 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 800, SD 808, SD 810, ...

CVE-2016-10495

CVE-2016-10495 affects Android on Qualcomm Snapdragon Mobile MDM9635M prior to the 2018-04-05 security patch level. The description states that changes were made to map the scan type value to an index value that is in range, implying a flaw in value handling within the affected component. The con...

CVE-2014-10048

CVE-2014-10048 affects Android on Qualcomm Snapdragon mobile/wear platforms (numerous SKUs) prior to the 2018-04-05 security patch level. The issue arises in time-services when setting offsets, where bases can be configured to values greater than the valid base, causing an array index out-of-boun...

CVE-2014-9991

CVE-2014-9991 describes a buffer overflow in Qualcomm closed-source Android components when USB mass storage transfers exceed 16kB. Public sources (CNVD-2018-08826, NVD entry) tie this issue to Android devices using Qualcomm Snapdragon/mobile platforms (e.g., MDM9206/9625/9635M/etc., SD series) a...

CVE-2015-9186

In Android before 2018-04-05 or earlier security patch level on Qualcomm Snapdragon Automobile, Snapdragon Mobile, and Snapdragon Wear MDM9206, MDM9650, MSM8909W, 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 800, SD 808, SD 810, ...

CVE-2015-9136

In Android before 2018-04-05 or earlier security patch level on Qualcomm Snapdragon Mobile and Snapdragon Wear MDM9206, MDM9607, MDM9640, MDM9650, SD 210/SD 212/SD 205, SD 425, SD 430, SD 450, SD 600, SD 625, SD 650/52, SD 808, SD 810, SD 820, SD 835, and SDX20, in pre-auth request, Host driver...

CVE-2015-9132

In Android before 2018-04-05 or earlier security patch level on Qualcomm Snapdragon Mobile and Small Cell SoC FSM9055, SD 210/SD 212/SD 205, SD 400, SD 410/12, SD 615/16/SD 415, SD 800, and SD 810, possible arbitrary memory read due to untrusted pointer dereference when handling HLOS controlled...

CVE-2016-10456

In Android before 2018-04-05 or earlier security patch level on Qualcomm Snapdragon Mobile and Snapdragon Wear MDM9206, MDM9607, MDM9615, MDM9635M, MDM9640, MDM9650, MSM8909W, SD 210/SD 212/SD 205, SD 400, SD 410/12, SD 425, SD 430, SD 450, SD 600, SD 615/16/SD 415, SD 617, SD 625, SD 650/52, SD...

CVE-2015-9131

CVE-2015-9131 corresponds to an input validation flaw in Qualcomm’s qsee on Android devices, affecting Snapdragon targets (SD 400/410/12, 615/16/SD 415, 800, 808, 810). The issue can enable unauthorized memory access due to lack of input validation. Public details in the connected documents show ...

CVE-2016-10485

CVE-2016-10485 is a buffer overflow vulnerability described as due to lack of proper bounds checking in Android on Qualcomm Snapdragon/mobile components (lists include IPQ4019, MDM9xxx, MSM8xxx, SD 210/212/205, SD 400/410/12, SD 615/16/415, SD 617, SD 650/52, SD 800, SD 808, SD 810, SDX20). The w...

CVE-2016-10482

CVE-2016-10482 affects Android devices on Qualcomm Snapdragon Mobile and Snapdragon Wear platforms prior to 2018-04-05 (or earlier patch levels). The issue occurs while processing downlink information, where an assert can be reached. Affected families include MDM9206/9607/9625/9635M/9640/9645/965...

CVE-2015-9123

CVE-2015-9123 affects many Qualcomm/Android components where code to zeroize the AES key could be optimized away by the compiler, potentially causing information disclosure. The issue is described as an information disclosure vulnerability that could occur on Android devices with affected Snapdra...

CVE-2015-9201

CVE-2015-9201 describes an integer overflow in tzbsp that can lead to privilege escalation on multiple Qualcomm Snapdragon/Android platforms (Automotive, Mobile, Wear, and related SoCs). The affected components and devices span Qualcomm’s tzbsp-related code paths used in Snapdragon lines (e.g., I...

CVE-2015-9119

Technical details about CVE-2015-9119 are not publicly provided in the connected documents. Affected products, exploitation, and fixes are not specified here. Monitor for updates from the sources in the Initial document (Android bulletin, NVD) for remediation.

CVE-2015-9145

CVE-2015-9145 affects Android devices with Qualcomm Snapdragon automotive/mobile/wear platforms (e.g., MDM92xx, SDxx family). The issue arises from a lack of input validation in NPA driver functions, enabling a null pointer dereference. Public details confirm the affected product families and pat...

CVE-2015-9118

CVE-2015-9118 affects Android systems with Qualcomm ADSP QDI Root-PD driver in Snapdragon SoCs (e.g., MDM9615/9625/9635M; SD 400/410/12/615/16/SD 415/800/808/810). The vulnerability arises from untrusted arguments from User PD that may cause integer overflow, leading to a buffer overflow. This is...

CVE-2016-10448

CVE-2016-10448 affects Android on Qualcomm Snapdragon platforms (multiple SoCs) where addSA/updateSA commands on the same SA can race. The root cause is that APIs addSA and updateSA access the global ipsec_sa_list[] without mutex protection, enabling memory corruption under concurrent operations....

CVE-2016-10419

CVE-2016-10419 affects Android devices using Qualcomm Snapdragon mobile platforms (e.g., MDM9640/9645/9650/9655, SD 450/625/650/52/820/835/845/850, SDX20). The issue is an out-of-bounds access during the initialization of a scheduler object service request caused by an uninitialized object number...