Qualcomm MDM9655 Firmware vulnerabilities
243 CVEs affecting Qualcomm MDM9655 Firmware, 0 known to be exploited (CISA KEV), with EPSS scores. Latest: CVE-2026-25262, published 2026-09-22.
More from Qualcomm.
Highest priority
Known exploited (CISA KEV) first, then by EPSS exploit probability.
- CVE-2020-11301, published 2021-09-08. High severity, CVSS 7.5. EPSS: 11.1% chance of exploitation in the next 30 days. Improper authentication of un-encrypted plaintext Wi-Fi frames in an encrypted network can lead to information disclosure in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon…
- 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-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-2015-9201, published 2018-04-18. Critical severity, CVSS 9.8. EPSS: 1.4% chance of exploitation in the next 30 days. In Android before 2018-04-05 or earlier security patch level on Qualcomm Snapdragon Automobile, Snapdragon Mobile, and Snapdragon Wear IPQ4019, MDM9206, MDM9607, MDM9625, MDM9635M, MDM9640, MDM9645,…
- CVE-2015-9122, published 2018-04-18. Critical severity, CVSS 9.8. EPSS: 1.4% chance of exploitation in the next 30 days. In Android before 2018-04-05 or earlier security patch level on Qualcomm Snapdragon Mobile and Snapdragon Wear MDM9206, MDM9607, MDM9635M, MDM9640, MDM9645, MDM9655, MSM8909W, SD 210/SD 212/SD 205,…
- CVE-2015-9145, published 2018-04-18. Critical severity, CVSS 9.8. EPSS: 1.4% chance of exploitation in the next 30 days. In Android before 2018-04-05 or earlier security patch level on Qualcomm Snapdragon Automobile, Snapdragon Mobile, and Snapdragon Wear MDM9206, MDM9607, MDM9635M, MDM9640, MDM9645, MDM9650, MDM9655,…
- CVE-2018-11945, published 2019-02-25. Critical severity, CVSS 9.8. EPSS: 1.4% chance of exploitation in the next 30 days. Improper input validation in wireless service messaging module for data received from broadcast messages can lead to heap overflow in Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer…
- CVE-2016-10491, published 2018-04-18. Critical severity, CVSS 9.8. EPSS: 1.3% chance of exploitation in the next 30 days. In Android before 2018-04-05 or earlier security patch level on Qualcomm Snapdragon Mobile and Snapdragon Wear MDM9206, MDM9607, MDM9625, MDM9635M, MDM9640, MDM9645, MDM9650, MDM9655, MSM8909W, SD…
- CVE-2015-9148, published 2018-04-18. Critical severity, CVSS 9.8. EPSS: 1.3% chance of exploitation in the next 30 days. In Android before 2018-04-05 or earlier security patch level on Qualcomm Snapdragon Automobile and Snapdragon Mobile MDM9625, MDM9635M, MDM9640, MDM9645, MDM9650, MDM9655, SD 400, SD 425, SD 430, SD…
- CVE-2016-10490, published 2018-04-18. Critical severity, CVSS 9.8. EPSS: 1.3% chance of exploitation in the next 30 days. In Android before 2018-04-05 or earlier security patch level on Qualcomm Snapdragon Automobile, Snapdragon Mobile, and Snapdragon Wear MDM9206, MDM9607, MDM9625, MDM9635M, MDM9640, MDM9645, MDM9650,…
Latest
- CVE-2026-25262, published 2026-09-22. Medium severity, CVSS 6.3. EPSS: 0.1% chance of exploitation in the next 30 days. Memory corruption while processing a crafted ELF file in the Primary Bootloader.
- CVE-2022-33213, published 2023-03-10. High severity, CVSS 8.8. EPSS: 0.4% chance of exploitation in the next 30 days. Memory corruption in modem due to buffer overflow while processing a PPP packet
- CVE-2022-25705, published 2023-03-10. High severity, CVSS 7.8. EPSS: 0.1% chance of exploitation in the next 30 days. Memory corruption in modem due to integer overflow to buffer overflow while handling APDU response
- CVE-2022-25682, published 2022-12-13. High severity, CVSS 7.8. EPSS: 0.1% chance of exploitation in the next 30 days. Memory corruption in MODEM UIM due to usage of out of range pointer offset while decoding command from card in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT,…
- CVE-2021-30344, published 2022-06-14. High severity, CVSS 7.5. EPSS: 0.6% chance of exploitation in the next 30 days. Improper authorization of a replayed LTE security mode command can lead to a denial of service in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon…
- CVE-2021-30342, published 2022-06-14. Medium severity, CVSS 5.9. EPSS: 0.5% chance of exploitation in the next 30 days. Improper integrity check can lead to race condition between tasks PDCP and RRC? after a valid RRC Command packet has been received in Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer IOT,…
- CVE-2021-30323, published 2022-02-11. High severity, CVSS 7.8. EPSS: 0.2% chance of exploitation in the next 30 days. Improper validation of maximum size of data write to EFS file can lead to memory corruption in Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon…
- CVE-2021-30322, published 2022-02-11. High severity, CVSS 7.8. EPSS: 0.2% chance of exploitation in the next 30 days. Possible out of bounds write due to improper validation of number of GPIOs configured in an internal parameters array in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon…
- CVE-2021-30271, published 2022-01-03. High severity, CVSS 7.8. EPSS: 0.2% chance of exploitation in the next 30 days. Possible null pointer dereference in trap handler due to lack of thread ID validation before dereferencing it in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer…
- CVE-2021-30259, published 2021-11-12. High severity, CVSS 7.8. EPSS: 0.2% chance of exploitation in the next 30 days. Possible out of bound access due to improper validation of function table entries in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT,…