Qualcomm
46,786 known vulnerabilities
Top Products
Improper validation of buffer size input to the EFS file can lead to memory corruption in Snapdragon Auto, Snapdragon Co
Possible assertion due to improper validation of OTA configuration in Snapdragon Auto, Snapdragon Compute, Snapdragon Co
Possible buffer overflow due to improper data validation of external commands sent via DIAG interface in Snapdragon Auto
Possible assertion due to improper validation of TCI configuration in Snapdragon Auto, Snapdragon Compute, Snapdragon Co
Possible assertion due to improper validation of invalid NR CSI-IM resource configuration in Snapdragon Auto, Snapdragon
Improper cleaning of secure memory between authenticated users can lead to face authentication bypass in Snapdragon Auto
Improper handling of permissions of a shared memory region can lead to memory corruption in Snapdragon Auto, Snapdragon
Possible use after free scenario in compute offloads to DSP while multiple calls spawn a dynamic process in Snapdragon A
Possible null pointer dereference due to lack of WDOG structure validation during registration in Snapdragon Auto, Snapd
Possible integer overflow due to improper fragment datatype while calculating number of fragments in a request message i
Improper validation of data length received from DMA buffer can lead to memory corruption. in Snapdragon Auto, Snapdrago
Lack of null check while freeing the device information buffer in the Bluetooth HFP protocol can lead to a NULL pointer
Possible assertion due to improper size validation while processing the DownlinkPreemption IE in an RRC Reconfiguration/
Possible out of bound access of DCI resources due to lack of validation process and resource allocation in Snapdragon Au
Possible out of bound write due to lack of boundary check for the maximum size of buffer when sending a DCI packet to re
Improper validation of maximum size of data write to EFS file can lead to memory corruption in Snapdragon Auto, Snapdrag
Possible out of bounds write due to improper validation of number of GPIOs configured in an internal parameters array in
Improper validation of input when provisioning the HDCP key can lead to memory corruption in Snapdragon Auto, Snapdragon
Improper validation of program headers containing ELF metadata can lead to image verification bypass in Snapdragon Auto,
Improper size validation of QXDM commands can lead to memory corruption in Snapdragon Compute, Snapdragon Consumer IOT,
Improper validation of function pointer type with actual function signature can lead to assertion in Snapdragon Auto, Sn
Possible null pointer dereference due to improper validation of APE clip in Snapdragon Auto, Snapdragon Compute, Snapdra
Possible integer overflow due to improper validation of command length parameters while processing WMI command in Snapdr
Lack of validation for third party application accessing the service can lead to information disclosure in Snapdragon Au
Use after free condition can occur in wired connectivity due to a race condition while creating and deleting folders in
Possible heap overflow due to lack of index validation before allocating and writing to heap buffer in Snapdragon Auto,
Possible buffer overflow while printing the HARQ memory partition detail due to improper validation of buffer size in Sn
Possible denial of service due to improper validation of DNS response when DNS client requests with PTR, NAPTR or SRV qu
Possible denial of service due to out of memory while processing RRC and NAS OTA message in Snapdragon Auto, Snapdragon
Possible denial of service due to incorrectly decoding hex data for the SIB2 OTA message and assigning a garbage value t
Possible assertion due to improper validation of symbols configured for PDCCH monitoring in Snapdragon Auto, Snapdragon
Improper validation of memory region in Hypervisor can lead to incorrect region mapping in Snapdragon Auto, Snapdragon C
Possible memory corruption in BT controller when it receives an oversized LMP packet over 2-DH1 link and leads to denial
An out of bound memory access can occur due to improper validation of number of frames being passed during music playbac
Improper validation of LLM utility timers availability can lead to denial of service in Snapdragon Auto, Snapdragon Comp
Possible use after free when process shell memory is freed using IOCTL call and process initialization is in progress in
Possible out of bound read due to lack of domain input validation while processing APK close session request in Snapdrag
Possible assertion in QOS request due to improper validation when multiple add or update request are received simultaneo
Possible buffer overflow due to lack of buffer length check when segmented WMI command is received in Snapdragon Auto, S
Possible out of bound access due to improper validation of item size and DIAG memory pools data while switching between
Possible assertion due to lack of input validation in PUSCH configuration in Snapdragon Auto, Snapdragon Compute, Snapdr
Possible buffer overflow due to lack of range check while processing a DIAG command for COEX management in Snapdragon Au
Possible denial of service due to improper handling of debug register trap from user applications in Snapdragon Consumer
Possible out of bound write in RAM partition table due to improper validation on number of partitions provided in Snapdr
Possible access control violation while setting current permission for VMIDs due to improper permission masking in Snapd
Improper input validation in TrustZone memory transfer interface can lead to information disclosure in Snapdragon Auto,
Improper access control while doing XPU re-configuration dynamically can lead to unauthorized access to a secure resourc
Possible integer overflow in page alignment interface due to lack of address and size validation before alignment in Sna
Possible integer overflow in access control initialization interface due to lack and size and address validation in Snap
Possible assertion due to improper handling of IPV6 packet with invalid length in destination options header in Snapdrag
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