Qualcomm MDM9628 Firmware vulnerabilities

267 CVEs affecting Qualcomm MDM9628 Firmware, 3 known to be exploited (CISA KEV), with EPSS scores. Latest: CVE-2026-57554, published 2026-10-06.

More from Qualcomm.

Highest priority

Known exploited (CISA KEV) first, then by EPSS exploit probability.

• CVE-2021-1905: Qualcomm Multiple Chipsets Use-After-Free Vulnerability, published 2021-05-07. High severity, CVSS 7.8. Actively exploited: in CISA KEV since 2021-11-03. EPSS: 1.5% chance of exploitation in the next 30 days. Possible use after free due to improper handling of memory mapping of multiple processes simultaneously. in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT,…
• 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-2021-1906: Qualcomm Multiple Chipsets Detection of Error Condition Without Action Vulnerability, published 2021-05-07. Medium severity, CVSS 5.5. Actively exploited: in CISA KEV since 2021-11-03. EPSS: 0.5% chance of exploitation in the next 30 days. Improper handling of address deregistration on failure can lead to new GPU address allocation failure. in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT,…
• 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-2021-30351, published 2022-01-03. Critical severity, CVSS 9.8. EPSS: 4% chance of exploitation in the next 30 days. An out of bound memory access can occur due to improper validation of number of frames being passed during music playback in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon…
• CVE-2022-40507, published 2023-06-06. High severity, CVSS 7.8. EPSS: 1.3% chance of exploitation in the next 30 days. Memory corruption due to double free in Core while mapping HLOS address to the list.
• CVE-2020-11192, published 2021-03-17. Critical severity, CVSS 9.8. EPSS: 1.1% chance of exploitation in the next 30 days. Out of bound write while parsing SDP string due to missing check on null termination in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial…
• CVE-2020-11190, published 2021-03-17. Critical severity, CVSS 9.1. EPSS: 1% chance of exploitation in the next 30 days. Buffer over-read can happen while parsing received SDP values due to lack of NULL termination check on SDP in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT,…
• CVE-2020-11189, published 2021-03-17. Critical severity, CVSS 9.1. EPSS: 1% chance of exploitation in the next 30 days. Buffer over-read can happen while parsing received SDP values due to lack of NULL termination check on SDP in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT,…
• CVE-2020-11188, published 2021-03-17. Critical severity, CVSS 9.1. EPSS: 1% chance of exploitation in the next 30 days. Buffer over-read can happen while parsing received SDP values due to lack of NULL termination check on SDP in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT,…

Latest

• CVE-2026-57554, published 2026-10-06. High severity, CVSS 7.8. EPSS: 0.1% chance of exploitation in the next 30 days. Memory Corruption when asynchronous threads access shared performance counter data simultaneously during FastRPC invocations.
• CVE-2026-24088, published 2026-06-01. High severity, CVSS 8.2. EPSS: 0.1% chance of exploitation in the next 30 days. Cryptographic Issue while processing a specific partition which allows unauthorized write access to load a customized bootloader.
• CVE-2026-24082, published 2026-05-04. High severity, CVSS 7.8. EPSS: 0.1% chance of exploitation in the next 30 days. Memory Corruption when copying data from a freed source while executing performance counter deselect operation.
• 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-59600, published 2026-03-02. High severity, CVSS 7.8. EPSS: 0.1% chance of exploitation in the next 30 days. Memory Corruption when adding user-supplied data without checking available buffer space.
• 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.