9148 matches found
CVE-2018-11948
Exceeding the limit of usage entries are not tracked and the information will be lost causing the content to lose continuity in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer Electronics Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdrago...
CVE-2018-13914
CVE-2018-13914 describes a lack of input validation for data from user space that can cause an out-of-bounds array issue on Qualcomm Snapdragon platforms (Auto, Consumer IOT, Industrial IOT, Mobile, Wearables) across listed SoCs (MDM9150, MDM9206, MDM9607, MDM9650, MSM8909W, MSM8996AU, SD 210/SD ...
CVE-2018-11932
CVE-2018-11932 involves improper input validation that could allow RW access from the host OS to a secure subsystem in Snapdragon Auto, Compute, Connectivity, and related Snapdragon devices (MDM9650/9655, MSM8996AU, QCS605, SD 410/12, SD 615/16/SD 415, SD 675, SD 712/710/670, SD 820/820A/835/845/...
CVE-2018-11820
CVE-2018-11820 concerns a side-channel leak caused by using a non-time-constant memcmp function in Qualcomm/Snapdragon components. Affected platforms include Snapdragon Auto/Compute/Connectivity, Snapdragon IoT lines and many SDM/SD/SDM variants (e.g., IPQ8074, MDM9150, MDM9206, MDM9607, MDM9640,...
CVE-2018-13900
Use-after-free vulnerability will occur as there is no protection for the route tables rule in IPA driver in Snapdragon Auto, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables in versions MDM9150, MDM9206, MDM9607, MDM9640,...
CVE-2018-11845
CVE-2018-11845 describes the use of non-time-constant comparison functions in Qualcomm Snapdragon components (across numerous Snapdragon Auto/Compute/Connectivity lines and device families such as MDM9150, MDM9206, MDM9607, MDM9650, MDM9655, MSM8996AU, QCS605, SDs 210–835, SD 8CX, and related SKU...
CVE-2018-13912
Arbitrary write issue can occur when user provides kernel address in compat mode in Snapdragon Auto, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables in MDM9150, MDM9206, MDM9607, MDM9640, MDM9650,...
CVE-2018-5839
The CVE-2018-5839 issue is a memory protection flaw in Qualcomm Snapdragon environments that permits local read/write of the modem image from the host OS kernel. Affected products include Snapdragon Auto, Compute, Consumer IoT, Industrial IoT, and Mobile lines across multiple SoCs (MDM9150, MDM96...
CVE-2018-11864
CVE-2018-11864 affects Qualcomm Snapdragon family devices (multiple SKUs) where bytes can be written to fuses from the Secure region and later read by the high-level OS. The description lists affected products/SoCs (e.g., IPQ8074, MDM9xxx, SD 210–SD 835, SDM/SD series, etc.) and indicates the iss...
CVE-2018-11945
Improper input validation in wireless service messaging module for data received from broadcast messages can lead to heap overflow in Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer Electronics Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon IoT, Snapdragon...
CVE-2018-5839
Improperly configured memory protection allows read/write access to modem image from HLOS kernel in Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile in versions MDM9150, MDM9615, MDM9625, MDM9635M, MDM9640, MDM9650, MDM9655, MSM8996AU,...
CVE-2018-13913
CVE-2018-13913 describes an unauthorized access vulnerability caused by improper validation of an array index while processing debugFS in Qualcomm Snapdragon components. The CNVD entry (CNVD-2019-05662) specifies this vulnerability as affecting multiple Qualcomm products and variants, including M...
CVE-2018-11845
Usage of non-time-constant comparison functions can lead to information leakage through side channel analysis in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer Electronics Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile,...
CVE-2018-11931
Improper access to HLOS is possible while transferring memory to CPZ in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer Electronics Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music in versions MDM9150,...
CVE-2018-13905
CVE-2018-13905 concerns a use-after-free in KGSL syncsource cleanup caused by an improperly handled syncsource lock. Affected Qualcomm/Snapdragon stack includes Snapdragon Auto, Snapdragon Consumer IoT, Industrial IoT, Mobile, Wearables across multiple silicon/board revisions (e.g., SD 210/212/20...
CVE-2018-11938
Improper input validation for argument received from HLOS can lead to buffer overflows and unexpected behavior in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer Electronics Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon IoT,...
CVE-2018-13904
Improper input validation in SCM handler to access storage in TZ can lead to unauthorized access in Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer Electronics Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile in versions MDM9206, MDM9607, MDM9650,...
CVE-2018-13900
CVE-2018-13900 is a use-after-free vulnerability in the IPA driver’s route table handling, where there is no protection for the route rule. Affected are Snapdragon platforms across multiple product families (e.g., Snapdragon Auto, Consumer IoT, Industrial IoT, Mobile, Voice & Music, Wearables) an...
CVE-2018-11864
Bytes can be written to fuses from Secure region which can be read later by HLOS in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer Electronics Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdrag...
CVE-2018-11935
CVE-2018-11935 affects Qualcomm Snapdragon devices (MDM9607/9650/9655, MSM8996AU, QCS605, SD 210–SD 415/SD 636/675/712 etc.) across Snapdragon Auto, Compute, Connectivity, and IoT lines. The issue is improper input validation in the Snapdragon stack that can cause an incorrect app id to be return...