Qualcomm
2,286 known vulnerabilities
Top Products
Memory Corruption when processing untrusted user input in the fastboot command handler for audio framework configuration
Memory Corruption when processing Device Capability Extended attributes in certain NAN Service Discovery Frames with inv
Transient DOS when processing a short target wake time channel usage response frame with insufficient packet size.
Weak configuration when UE does not verify the consistency of its additional security capabilities with the replayed cap
Memory Corruption while processing IOCTL device driver requests with invalid arguments.
Memory Corruption when handling malformed request parameters in the fingerprint TA.
Cryptographic Issue while processing registration requests with malformed or missing authentication parameters.
Information Disclosure when IPSec negotiation fails or is not established properly during NG-eCall SIP signaling.
Information Disclosure when processing wireless network channel switch information with improperly formatted length fiel
Memory Corruption when processing registry values with incorrect types using a direct query method.
Memory corruption while processing a packet with a size close to the maximum allowed value.
Memory Corruption when processing asynchronous input parameters due to improper handling of modified values between chec
Memory Corruption when processing invalid HT40 channel layouts during dynamic channel switching operations.
Memory Corruption when updating prepared commands with invalid port indices based on user space input exceeds supported
Cryptographic Issue when using a static initialization vector for AES-GCM key wrapping, which requires a unique value fo
Memory Corruption when allocating memory with sizes that exceed the maximum allowed value.
Memory Corruption when validating input batch size and buffer plane count exceeds maximum allowed values.
Memory Corruption when handling flash commands due to outdated LED count values being used after userspace modification.
Memory Corruption when parsing jpeg commands due to unaccounted extra writes to the buffer during validation checks.
Memory Corruption when processing multiple IOCTL calls with the same buffer file descriptor input.
Memory Corruption when processing multiple IOCTL calls with the same buffer file descriptor input due to accessing alrea
Memory Corruption when invoking device input/output control operations for mapping and unmapping persistent memory buffe
Memory corruption while using Strongbox due to buffer overflow.
Memory corruption while using Strongbox due to missing bounds check.
Memory Corruption when accessing shared buffers without validation of concurrent user-mode input modifications.
Memory corruption while processing multiple IOCTL command for escape operations.
Memory corruption while processing IOCTL calls for escape operations.
Memory Corruption when processing fastboot commands to set display mode.
Memory corruption while processing fastboot commands with improperly formatted input.
Cryptographic issue while processing partition table entries allows unauthorized modification of boot flow.
Memory corruption while processing fastboot commands with invalid input.
Cryptographic Issue while processing a specific partition which allows unauthorized write access to load a customized bo
Memory corruption while processing fastboot OEM commands.
Memory Corruption when processing display command line information due to improper initialization of a variable.
Memory Corruption when sending random number generator command with insufficient output buffer size.
Memory Corruption when output buffer size is smaller than input buffer size during data copying operation.
Memory corruption in windows drivers while sending incorrect trusted application request
Memory corruption in diagnostic services due to absence of input validation
Memory Corruption when processing IOCTL requests with mismatched API versions due to concurrent modification of user-spa
Information Disclosure when processing advertisement frames with malformed MBSSID elements of insufficient length.
Memory Corruption when writing to invalid memory locations occurs due to heap memory exhaustion during secure data initi
Memory Corruption when processing device identifier strings that exceed the expected maximum length.
Memory Corruption when running a memory copy operation due to invalid writes caused by a null pointer.
Information Disclosure when resetting device to factory default settings through powerline interface allows unauthorized
Buffer overflow due to incorrect authorization in PLC FW
Memory corruption while processing IOCTL command when device is in power-save state.
Memory Corruption when copying data from a freed source while executing performance counter deselect operation.
Memory corruption when another driver calls an IOCTL with invalid input/output buffer.
Memory corruption while creating a process on the digital signal processor due to allocation failure at the kernel level
Information Disclosure while processing IOCTL handler callbacks without verifying buffer size.
Frequently Asked Questions
How many CVEs affect Qualcomm?
Qualcomm has 2,286 CVE records in our database, including 22 critical and 1506 high severity vulnerabilities. 1 of these are listed in CISA's Known Exploited Vulnerabilities catalog.
What are the most severe Qualcomm vulnerabilities?
Qualcomm has 22 critical severity (CVSS 9.0+) and 1506 high severity (CVSS 7.0-8.9) vulnerabilities. 1 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