CVE-2015-9158

The CVE-2015-9158 issue involves a buffer overflow in a QTEE crypto function on Android devices using Qualcomm Snapdragon platforms (e.g., Snapdragon Automobile, Mobile, Wear and various SD/SoC families). Root cause: a vulnerability in the QTEE crypto function that can overflow a buffer, potentia...

CVE-2016-10414

In Android before 2018-04-05 or earlier security patch level on Qualcomm Small Cell SoC, Snapdragon Automobile, Snapdragon Mobile, and Snapdragon Wear FSM9055, IPQ4019, MDM9206, MDM9607, MDM9625, MDM9635M, MDM9640, MDM9645, MDM9650, MDM9655, MSM8909W, SD 210/SD 212/SD 205, SD 400, SD 410/12, SD...

CVE-2016-10476

In Android before 2018-04-05 or earlier security patch level on Qualcomm Snapdragon Mobile and Snapdragon Wear MDM9206, MDM9607, 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, SD 820, SD 835,...

CVE-2015-9160

In Android before 2018-04-05 or earlier security patch level on Qualcomm Snapdragon Automobile, Snapdragon Mobile, and Snapdragon Wear MDM9206, MDM9607, MDM9635M, 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 80...

CVE-2016-10473

The CVE-2016-10473 entry describes a buffer overflow in a Qualcomm Snapdragon-based Android platform's supplementary services function, affecting Android versions prior to patch levels 2018-04-01/2018-04-05. Affected devices include Snapdragon Mobile and Snapdragon Wear families (e.g., MDM9206, M...

CVE-2015-9210

CVE-2015-9210 affects Android devices using Qualcomm Snapdragon components (including Snapdragon Automobile, Mobile, Wear, and various SD variants listed). The issue is a lack of input validation in playready_licacq_process_response(), which can lead to memory over-read. The cited CVSS v3.0 metri...

CVE-2015-9205

In CVE-2015-9205, a buffer over-read can occur in a PlayReady API function on Android devices with Qualcomm SD series (MSM8909W, SD210/SD212/SD205, SD410/12, SD615/16/SD415, SD808, SD810). The issue affects Android before 2018-04-05 or earlier patch levels; CVSS indicates a critical impact (high ...

CVE-2015-9197

Mode C: CVE-2015-9197 affects various Qualcomm Snapdragon/mobile SoCs (e.g., MDM9xxx, SD 210–618 families) when enabling XPUs for SMEM partitions. If XPUs configuration values are out of range, memory access outside SMEM can occur and set incorrect XPU configurations, potentially enabling remote ...

CVE-2015-9212

The CVE-2015-9212 issue affects Qualcomm Snapdragon platforms (Mobile and Wear MSM8909W; SD 210/212/205; SD 400; SD 410/12; SD 800). Root cause: lack of input validation while processing TZ_PR_CMD_SAVE_KEY leads to a buffer overread. Impact is described as high across confidentiality, integrity, ...

CVE-2015-9223

CVE-2015-9223 describes a buffer overflow in Android prior to the 2018-04-05 security patch level when processing an audio buffer on Qualcomm Snapdragon mobile platforms (MDM9615, MDM9625, MDM9635M, SD 400/600/800). The issue affects Android devices using these Qualcomm components and could enabl...

CVE-2014-9985

CVE-2014-9985 affects Android on Qualcomm Snapdragon platforms (MDM9635M, SD 400, SD 800). The vulnerability arises from a TOCTOU race condition that can bypass error-condition checks, causing undefined behavior in the affected components. Based on the initial and linked references, the issue is ...

CVE-2016-10472

CVE-2016-10472 affects Qualcomm Snapdragon mobile and wearable SoCs (e.g., MDM9206/9607/9650, MSM8909W, SD 210/212/205, 400, 410/12, 425, 430, 450, 600, 615/16/415, 617, 625, 650/52, 800, 808, 810, 820, 835, SDX20). Root cause: HLOS kernel failed to check address and size passed to TZ_INFO_GET_SE...

CVE-2016-10483

CVE-2016-10483 affects Android devices with Qualcomm Snapdragon Mobile SoCs (SD 410/12, SD 615/16, SD 415, SD 808, SD 810). Root cause is improper input validation while processing SCM Command, leading to unauthorized memory access. According to the Android bulletin, these issues were addressed w...

CVE-2016-10430

CVE-2016-10430 affects Android on certain Qualcomm platforms (Snapdragon Automobile and Snapdragon Mobile) prior to the 2018-04-05 patch level. The issue arises when a TA (trusted application) that has privileges to the CPVC MINK class executes and is able to access methods exposed by the CPVC in...

CVE-2016-10437

CVE-2016-10437 is an information-disclosure vulnerability affecting Android devices with Qualcomm networking components. In affected Android versions prior to 2018-04-05 patch level (and related patches for various Qualcomm SoCs such as Small Cell, Snapdragon Mobile/Wear families and SDR devices ...

CVE-2016-10438

CVE-2016-10438 is an information exposure issue in Android devices affected by Qualcomm Small Cell SoC, Snapdragon Mobile and Wear FSM9055, IPQ4019/IPQ8064, and various SD/SoC families. The root cause is logging of debug statements using %p, which could expose kernel or driver pointers. The repor...

CVE-2016-10426

CVE-2016-10426 documents a buffer overflow in SafeSwitch affecting Android devices powered by Qualcomm Snapdragon (Automobile and Mobile) across multiple SD cores (410/12, 425, 430, 450, 617, 625, 650/52, 810, 820, 820A). Root cause is a buffer overflow in SafeSwitch; exploitation details are not...

CVE-2015-9183

CVE-2015-9183 affects Android devices built with Qualcomm Snapdragon chips (SD 410/12, SD 617, SD 650/52, SD 800, SD 808, SD 810). In the TQS QSEE application, parsing the "Set Certificates" command can trigger an integer overflow that may overflow a buffer. This is described as a high-severity, ...

CVE-2015-9178

CVE-2015-9178 is a memory-corruption issue affecting Android devices with Qualcomm Snapdragon SoCs (incl. Snapdragon Automobile, Mobile, Wear families and related SD ranges up to SD 850) when processing the rmp secure command. The vulnerability allows memory corruption if the response buffer is s...

CVE-2015-9166

CVE-2015-9166 concerns DRM provisioning in QSEE-based components on Qualcomm Snapdragon platforms. The issue arises because the finalize_prov_flag.data mechanism, intended to prevent further provisioning after initial provisioning, is not sufficiently checked, allowing provisioning to proceed eve...