Qualcomm
46,786 known vulnerabilities
Top Products
Possible stack buffer overflow due to lack of check on the maximum number of post NAN discovery attributes while process
Possible buffer overflow due to lack of length check of source and destination buffer before copying in Snapdragon Auto,
Possible memory corruption due to lack of bound check of input index in Snapdragon Auto, Snapdragon Compute, Snapdragon
Possible integer overflow due to improper check of batch count value while sanitizer is enabled in Snapdragon Auto, Snap
Null pointer dereference can occur due to lack of null check for user provided input in Snapdragon Auto, Snapdragon Comp
Improper access control in trusted application environment can cause unauthorized access to CDSP or ADSP VM memory with
Null pointer dereference can occur due to memory allocation failure in DIAG in Snapdragon Auto, Snapdragon Compute, Snap
Possible integer overflow due to improper length check while updating grace period and count record in Snapdragon Auto,
Accepting AMSDU frames with mismatched destination and source address can lead to information disclosure in Snapdragon A
A lack of replay attack protection in GUTI REALLOCATION COMMAND message process in Qualcomm modem prior to SMR Oct-2021
Possible integer and heap overflow due to lack of input command size validation while handling beacon template update co
Possible Integer overflow to buffer overflow issue can occur due to improper validation of input parameters when extscan
A use after free can occur due to improper validation of P2P device address in PD Request frame in Snapdragon Auto, Snap
Use-after-free vulnerability in kernel graphics driver because of storing an invalid pointer in Snapdragon Compute, Snap
Null pointer dereference occurs due to improper validation when the preemption feature enablement is toggled in Snapdrag
Possible heap overflow due to improper validation of local variable while storing current task information locally in Sn
Potential null pointer dereference in KGSL GPU auxiliary command due to improper validation of user input in Snapdragon
Possible null pointer dereference due to race condition between timeline fence signal and time line fence destroy in Sna
Possible buffer over read due to lack of alignment between map or unmap length of IPA SMMU and WLAN SMMU in Snapdragon A
Possible assertion due to lack of physical layer state validation in Snapdragon Auto, Snapdragon Compute, Snapdragon Con
Possible use-after-free due to lack of validation for the rule count in filter table in IPA driver in Snapdragon Auto, S
Buffer Overflow while processing IOCTL for getting peripheral endpoint information there is no proper validation for inp
Possible buffer overflow due to lack of offset length check while updating the buffer value in Snapdragon Auto, Snapdrag
Improper handling of ASB-C broadcast packets with crafted opcode in LMP can lead to uncontrolled resource consumption in
A race condition in fastrpc kernel driver for dynamic process creation can lead to use after free scenario in Snapdragon
Improper Access Control when ACL link encryption is failed and ACL link is not disconnected during reconnection with pai
Improper handling of ASB-U packet with L2CAP channel ID by slave host can lead to interference with piconet in Snapdrago
Possible buffer over read occurs due to lack of length check of request buffer in Snapdragon Auto, Snapdragon Compute, S
Possible out of bound read due to lack of length check of data while parsing the beacon or probe response in Snapdragon
Null Pointer Dereference may occur due to improper validation while processing crafted SDP body in Snapdragon Auto, Snap
Possible buffer over read issue due to improper length check on WPA IE string sent by peer in Snapdragon Auto, Snapdrago
Possible null pointer dereference due to lack of validation check for passed pointer during key import in Snapdragon Aut
Possible memory corruption due to improper check when application loader object is explicitly destructed while applicati
UE assertion is possible due to improper validation of invite message with SDP body in Snapdragon Auto, Snapdragon Compu
Buffer overflow occurs in trusted applications due to lack of length check of parameters in Snapdragon Auto, Snapdragon
Possible buffer overflow due to improper validation of device types during P2P search in Snapdragon Auto, Snapdragon Com
Possible out of bounds read due to incorrect validation of incoming buffer length in Snapdragon Auto, Snapdragon Compute
Lack of strict validation of bootmode can lead to information disclosure in Snapdragon Auto, Snapdragon Compute, Snapdra
Buffer over read could occur due to incorrect check of buffer size while flashing emmc devices in Snapdragon Connectivit
Incorrect pointer argument passed to trusted application TA could result in un-intended memory operations in Snapdragon
Integer underflow can occur due to improper handling of incoming RTCP packets in Snapdragon Auto, Snapdragon Compute, Sn
Integer underflow can occur when the RTCP length is lesser than than the actual blocks present in Snapdragon Auto, Snapd
Possible buffer underflow due to lack of check for negative indices values when processing user provided input in Snapdr
Loop with unreachable exit condition may occur due to improper handling of unsupported input in Snapdragon Auto, Snapdra
Child process can leak information from parent process due to numeric pids are getting compared and these pid can be reu
Improper authentication of un-encrypted plaintext Wi-Fi frames in an encrypted network can lead to information disclosur
Improper authentication of Non-EAPOL/WAPI plaintext frames during four-way handshake can lead to arbitrary network packe
Possible out of bound read due to lack of length check of FT sub-elements in Snapdragon Auto, Snapdragon Compute, Snapdr
Possible buffer overflow due to lack of parameter length check during MBSSID scan IE parse in Snapdragon Auto, Snapdrago
Possible buffer over read due to improper validation of IE size while parsing beacon from peer device in Snapdragon Auto
Frequently Asked Questions
How many CVEs affect Qualcomm?
Qualcomm has 46,786 CVE records in our database, including 9787 critical and 28782 high severity vulnerabilities. 12 of these are listed in CISA's Known Exploited Vulnerabilities catalog.
What are the most severe Qualcomm vulnerabilities?
Qualcomm has 9787 critical severity (CVSS 9.0+) and 28782 high severity (CVSS 7.0-8.9) vulnerabilities. 12 vulnerabilities are confirmed as actively exploited in the wild.
How can I scan for Qualcomm vulnerabilities?
CyberStrike's AI-powered security agents automatically detect vulnerabilities in Qualcomm products across your infrastructure. The platform provides continuous pentesting, DAST scanning, and real-time vulnerability monitoring with actionable remediation guidance.
Detect Qualcomm Vulnerabilities
CyberStrike scans your infrastructure for Qualcomm vulnerabilities and provides real-time remediation guidance.
Get Started