Qualcomm CVEs
2,991 CVEs and advisories name Qualcomm as an affected vendor, 12 of them on CISA's Known Exploited Vulnerabilities catalog, newest first. Follow it as a feed.
- CVE-2019-14115u'Information disclosure issue occurs as in current logic as secure touch is released without clearing the display session which can result
- CVE-2019-14089u'Keymaster attestation key and device IDs provisioning which is a one time process is incorrectly allowed to be re-provisioned after a user
- CVE-2019-14074u'Heap overflow in diag command handler due to lack of check of packet length received from user' in Snapdragon Auto, Snapdragon Compute, Sn
- CVE-2019-14065u'Pointer double free in HavenSvc due to not setting the pointer to NULL after freeing it' in Snapdragon Auto, Snapdragon Compute, Snapdrago
- CVE-2019-14056u'Possible integer overflow in API due to lack of check on large oid range count in cert extension field' in Snapdragon Auto, Snapdragon Com
- CVE-2019-14052u'Accessing an uninitialized data structure could result in partially copying of contents and thus incorrect processing' in Snapdragon Auto,
- CVE-2019-14025u'When a new session is created, Object is returned that contains TZ addresses and it get passed to HLOS as an handle to refer to a particul
- CVE-2019-13999u'Lack of check for integer overflow for round up and addition operations result into memory corruption and potential information leakage' i
- CVE-2019-13998u'Lack of check that the TX FIFO write and read indices that are read from shared RAM are less than the FIFO size results into memory corrup
- CVE-2019-13995u'Lack of integer overflow check for addition of fragment size and remaining size that are read from shared memory can lead to memory corrup
- CVE-2019-13994u'Lack of check that the current received data fragment size of a particular packet that are read from shared memory are less than the actua
- CVE-2019-13992u'Out of bound memory access if stack push and pop operation are performed without doing a bound check on stack top' in Snapdragon Auto, Sna
- CVE-2019-10629u'User Process can potentially corrupt kernel virtual page by passing a crafted page in API' in Snapdragon Auto, Snapdragon Compute, Snapdra
- CVE-2019-10628u'Memory can be potentially corrupted if random index is allowed to manipulate TLB entries in Kernel from user library' in Snapdragon Auto,
- CVE-2019-10615u'Possibility of integer overflow in keymaster 4 while allocating memory due to multiplication of large numcerts value and size of keymaster
- CVE-2019-10596u'Improper access control can lead signed process to guess pid of other processes and access their address space' in Snapdragon Auto, Snapdr
- CVE-2019-10562u'Improper authentication and signature verification of debug polices in secure boot loader will allow unverified debug policies to be loade
- CVE-2019-10527u'SMEM partition can be manipulated in case of any compromise on HLOS, thus resulting in access to memory outside of SMEM address range whic
- CVE-2018-13903u'Error in UE due to race condition in EPCO handling' in Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer IOT, Snapdragon Industrial
- CVE-2020-3681Authenticated and encrypted payload MMEs can be forged and remotely sent to any HPAV2 system using a jailbreak key recoverable from code.
- CVE-2020-3701Use after free issue while processing error notification from camx driver due to not properly releasing the sequence data in Snapdragon Mobi
- CVE-2020-3700Possible out of bounds read due to a missing bounds check and could lead to local information disclosure in the wifi driver with no addition
- CVE-2020-3699Possible out of bound access while processing assoc response from host due to improper length check before copying into buffer in Snapdragon
- CVE-2020-3698Out of bound write while QoS DSCP mapping due to improper input validation for data received from association response frame in Snapdragon A
- CVE-2020-3688Possible buffer overflow while parsing mp4 clip with corrupted sample atoms due to improper validation of index in Snapdragon Auto, Snapdrag
- CVE-2020-3671Use-after-free issue could occur due to dangling pointer when generating a frame buffer in OpenGL ES in Snapdragon Compute, Snapdragon Consu
- CVE-2019-14130Memory corruption can occurs in trusted application if offset size from HLOS is more than actual mapped buffer size in Snapdragon Auto, Snap
- CVE-2019-14124Memory failure in content protection module due to not having pointer within the scope in Snapdragon Auto, Snapdragon Compute, Snapdragon Mo
- CVE-2019-14123Possible buffer overflow and over read possible due to missing bounds checks for fixed limits if we consider widevine HLOS client as non-tru
- CVE-2019-14101Out of bounds read can happen in diag event set mask command handler when user provided length in the command request is less than expected