Qualcomm
46,786 known vulnerabilities
Top Products
Transient DOS while connecting STA to AP and initiating ADD TS request from AP to establish TSpec session.
Memory corruption occurs while connecting a STA to an AP and initiating an ADD TS request.
Memory corruption occurs while connecting a STA to an AP and initiating an ADD TS request from the AP to establish a TSp
Memory corruption may occur due top improper access control in HAB process.
Memory corruption occurs when handling client calls to EnableTestMode through an Escape call.
Memory corruption while processing escape code in API.
Memory corruption while processing multiple IOCTL calls from HLOS to DSP.
Memory corruption can occur when TME processes addresses from TZ and MPSS requests without proper validation.
Cryptographic issue may arise because the access control configuration permits Linux to read key registers in TCSR.
Information disclosure may occur during a video call if a device resets due to a non-conforming RTCP packet that doesn`t
Cryptographic issue occurs during PIN/password verification using Gatekeeper, where RPMB writes can be dropped on verifi
Information disclosure while creating MQ channels.
Memory corruption while processing IOCTL calls to add route entry in the HW.
Memory corruption while accessing MSM channel map and mixer functions.
Memory corruption while invoking IOCTL map buffer request from userspace.
Memory corruption occurs during the copying of read data from the EEPROM because the IO configuration is exposed as shar
Memory corruption while handling file descriptor during listener registration/de-registration.
Cryptographic issues while generating an asymmetric key pair for RKP use cases.
Memory corruption while processing IOCTL calls.
There may be information disclosure during memory re-allocation in TZ Secure OS.
Memory corruption while assigning memory from the source DDR memory(HLOS) to ADSP.
Memory corruption while calling the NPU driver APIs concurrently.
Memory corruption occurs during an Escape call if an invalid Kernel Mode CPU event and sync object handle are passed wit
Memory corruption while doing Escape call when user provides valid kernel address in the place of valid user buffer addr
Memory corruption may occur in keyboard virtual device due to guest VM interaction.
Memory corruption while reading a type value from a buffer controlled by the Guest Virtual Machine.
Memory corruption while processing input message passed from FE driver.
Memory corruption while reading a value from a buffer controlled by the Guest Virtual Machine.
Memory corruption may occur while processing message from frontend during allocation.
Transient DOS may occur while processing the country IE.
Transient DOS can occur while processing UCI command.
Memory corruption in display driver while detaching a device.
Memory corruption may occur while accessing a variable during extended back to back tests.
Memory corruption may occur during communication between primary and guest VM.
Memory corruption may occur while validating ports and channels in Audio driver.
Memory corruption may occur due to improper input validation in clock device.
Information disclosure may occur due to improper permission and access controls to Video Analytics engine.
Memory corruption may occur during the synchronization of the camera`s frame processing pipeline.
Memory corruption while handling multuple IOCTL calls from userspace for remote invocation.
Memory corruption caused by missing locks and checks on the DMA fence and improper synchronization.
Memory corruption during voice activation, when sound model parameters are loaded from HLOS, and the received sound mode
Memory corruption during voice activation, when sound model parameters are loaded from HLOS to ADSP.
Memory corruption while invoking IOCTL calls from the use-space for HGSL memory node.
Memory corruption while processing command in Glink linux.
Transient DOS during hypervisor virtual I/O operation in a virtual machine.
Memory corruption while processing camera use case IOCTL call.
Information disclosure while deriving keys for a session for any Widevine use case.
While processing the authentication message in UE, improper authentication may lead to information disclosure.
Memory corruption while processing IOCTL from user space to handle GPU AHB bus error.
Memory corruption while Invoking IOCTL calls from user-space to validate FIPS encryption or decryption functionality.
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