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-2021-1968Improper validation of kernel buffer address while copying information back to user buffer can lead to kernel memory information exposure to
- CVE-2021-30261Possible integer and heap overflow due to lack of input command size validation while handling beacon template update command from HLOS in S
- CVE-2021-30260Possible Integer overflow to buffer overflow issue can occur due to improper validation of input parameters when extscan hostlist configurat
- CVE-2021-1976A use after free can occur due to improper validation of P2P device address in PD Request frame in Snapdragon Auto, Snapdragon Compute, Snap
- CVE-2021-1947Use-after-free vulnerability in kernel graphics driver because of storing an invalid pointer in Snapdragon Compute, Snapdragon Connectivity,
- CVE-2021-1939Null pointer dereference occurs due to improper validation when the preemption feature enablement is toggled in Snapdragon Auto, Snapdragon
- CVE-2021-30295Possible heap overflow due to improper validation of local variable while storing current task information locally in Snapdragon Auto, Snapd
- CVE-2021-30294Potential null pointer dereference in KGSL GPU auxiliary command due to improper validation of user input in Snapdragon Auto, Snapdragon Con
- CVE-2021-30290Possible null pointer dereference due to race condition between timeline fence signal and time line fence destroy in Snapdragon Auto, Snapdr
- CVE-2021-1974Possible buffer over read due to lack of alignment between map or unmap length of IPA SMMU and WLAN SMMU in Snapdragon Auto, Snapdragon Comp
- CVE-2021-1971Possible assertion due to lack of physical layer state validation in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdrago
- CVE-2021-1963Possible use-after-free due to lack of validation for the rule count in filter table in IPA driver in Snapdragon Auto, Snapdragon Compute, S
- CVE-2021-1962Buffer Overflow while processing IOCTL for getting peripheral endpoint information there is no proper validation for input maximum endpoint
- CVE-2021-1961Possible buffer overflow due to lack of offset length check while updating the buffer value in Snapdragon Auto, Snapdragon Compute, Snapdrag
- CVE-2021-1960Improper handling of ASB-C broadcast packets with crafted opcode in LMP can lead to uncontrolled resource consumption in Snapdragon Auto, Sn
- CVE-2021-1958A race condition in fastrpc kernel driver for dynamic process creation can lead to use after free scenario in Snapdragon Auto, Snapdragon Co
- CVE-2021-1957Improper Access Control when ACL link encryption is failed and ACL link is not disconnected during reconnection with paired device in Snapdr
- CVE-2021-1956Improper handling of ASB-U packet with L2CAP channel ID by slave host can lead to interference with piconet in Snapdragon Auto, Snapdragon C
- CVE-2021-1952Possible buffer over read occurs due to lack of length check of request buffer in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivi
- CVE-2021-1948Possible out of bound read due to lack of length check of data while parsing the beacon or probe response in Snapdragon Auto, Snapdragon Com
- CVE-2021-1946Null Pointer Dereference may occur due to improper validation while processing crafted SDP body in Snapdragon Auto, Snapdragon Compute, Snap
- CVE-2021-1941Possible buffer over read issue due to improper length check on WPA IE string sent by peer in Snapdragon Auto, Snapdragon Compute, Snapdrago
- CVE-2021-1935Possible null pointer dereference due to lack of validation check for passed pointer during key import in Snapdragon Auto, Snapdragon Comput
- CVE-2021-1934Possible memory corruption due to improper check when application loader object is explicitly destructed while application is unloading in S
- CVE-2021-1933UE assertion is possible due to improper validation of invite message with SDP body in Snapdragon Auto, Snapdragon Compute, Snapdragon Conne
- CVE-2021-1909Buffer overflow occurs in trusted applications due to lack of length check of parameters in Snapdragon Auto, Snapdragon Compute, Snapdragon
- CVE-2021-1972Possible buffer overflow due to improper validation of device types during P2P search in Snapdragon Auto, Snapdragon Compute, Snapdragon Con
- CVE-2021-1930Possible out of bounds read due to incorrect validation of incoming buffer length in Snapdragon Auto, Snapdragon Compute, Snapdragon Connect
- CVE-2021-1929Lack of strict validation of bootmode can lead to information disclosure in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Sn
- CVE-2021-1928Buffer over read could occur due to incorrect check of buffer size while flashing emmc devices in Snapdragon Connectivity, Snapdragon Consum