Qualcomm SDA660 Firmware vulnerabilities
422 CVEs affecting Qualcomm SDA660 Firmware, 1 known to be exploited (CISA KEV), with EPSS scores. Latest: CVE-2026-25275, published 2026-09-17.
More from Qualcomm.
Highest priority
Known exploited (CISA KEV) first, then by EPSS exploit probability.
- CVE-2026-21385: Qualcomm Multiple Chipsets Memory Corruption Vulnerability, published 2026-03-02. High severity, CVSS 7.8. Actively exploited: in CISA KEV since 2026-03-03. EPSS: 1.3% chance of exploitation in the next 30 days. Memory corruption while using alignments for memory allocation.
- CVE-2020-3657, published 2020-11-02. Critical severity, CVSS 9.8. EPSS: 28.3% chance of exploitation in the next 30 days. u'Remote code execution can happen by sending a carefully crafted POST query when Device configuration is accessed from a tethered client through webserver due to lack of array bound check.' in…
- CVE-2020-11206, published 2020-11-12. High severity, CVSS 7.8. EPSS: 1.8% chance of exploitation in the next 30 days. Possible buffer overflow in Fastrpc while handling received parameters due to lack of validation on input parameters' in Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer IOT, Snapdragon…
- CVE-2019-10529, published 2019-11-06. High severity, CVSS 8.1. EPSS: 1.7% chance of exploitation in the next 30 days. Possible use after free issue due to race condition while attempting to mark the entry pages as dirty using function set_page_dirty() in Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer IOT,…
- CVE-2019-10574, published 2020-04-16. High severity, CVSS 7.1. EPSS: 1.6% chance of exploitation in the next 30 days. Lack of boundary checks for data offsets received from HLOS can lead to out-of-bound read in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer Electronics…
- CVE-2019-2256, published 2019-06-14. Critical severity, CVSS 9.8. EPSS: 1.5% chance of exploitation in the next 30 days. An unprivileged user can craft a bitstream such that the payload encoded in the bitstream gains code execution in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer…
- CVE-2019-2255, published 2019-06-14. Critical severity, CVSS 9.8. EPSS: 1.5% chance of exploitation in the next 30 days. An unprivileged user can craft a bitstream such that the payload encoded in the bitstream gains code execution in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer…
- CVE-2020-11207, published 2020-11-12. High severity, CVSS 7.8. EPSS: 1.5% chance of exploitation in the next 30 days. Buffer overflow in LibFastCV library due to improper size checks with respect to buffer length' in Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon…
- CVE-2016-10502, published 2018-12-10. Critical severity, CVSS 9.8. EPSS: 1.5% chance of exploitation in the next 30 days. While generating trusted application id, An integer overflow can occur giving the trusted application an invalid identity in Snapdragon Mobile and Snapdragon Wear in versions MDM9206, MDM9607,…
- CVE-2019-2249, published 2019-11-06. Critical severity, CVSS 9.8. EPSS: 1.4% chance of exploitation in the next 30 days. Kernel can do a memory read from arbitrary address passed by user during execution of a syscall in Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon…
Latest
- CVE-2026-25275, published 2026-09-17. High severity, CVSS 7.5. EPSS: 0.2% chance of exploitation in the next 30 days. Transient DOS when processing authentication frames with invalid FILS information element header lengths.
- CVE-2026-24091, published 2026-06-01. High severity, CVSS 7.2. EPSS: 0.1% chance of exploitation in the next 30 days. Memory corruption while processing fastboot commands with improperly formatted input.
- CVE-2026-24085, published 2026-06-01. High severity, CVSS 7.2. EPSS: 0.1% chance of exploitation in the next 30 days. Memory Corruption when processing display command line information due to improper initialization of a variable.
- CVE-2025-59610, published 2026-06-01. Medium severity, CVSS 6.4. EPSS: 0.1% chance of exploitation in the next 30 days. Memory Corruption when processing IOCTL requests with mismatched API versions due to concurrent modification of user-space buffer.
- CVE-2025-47404, published 2026-05-04. High severity, CVSS 7.8. EPSS: 0.1% chance of exploitation in the next 30 days. Memory corruption when dynamically changing the size of a previously allocated buffer while its contents are being modified.
- CVE-2025-47386, published 2026-03-02. High severity, CVSS 7.8. EPSS: 0.1% chance of exploitation in the next 30 days. Memory Corruption while invoking IOCTL calls when concurrent access to shared buffer occurs.
- CVE-2025-47383, published 2026-03-02. High severity, CVSS 7.2. EPSS: 0.1% chance of exploitation in the next 30 days. Weak configuration may lead to cryptographic issue when a VoWiFi call is triggered from UE.
- CVE-2025-47379, published 2026-03-02. High severity, CVSS 7.8. EPSS: 0.1% chance of exploitation in the next 30 days. Memory Corruption when concurrent access to shared buffer occurs due to improper synchronization between assignment and deallocation of buffer resources.
- CVE-2025-47376, published 2026-03-02. High severity, CVSS 7.8. EPSS: 0.1% chance of exploitation in the next 30 days. Memory Corruption when concurrent access to shared buffer occurs during IOCTL calls.