Qualcomm
Qualcomm Qca6391 Firmware: vulnerabilities and CVEs
Qualcomm Qca6391 Firmware has 950 published vulnerabilities, 74 of them in the last 12 months. 93 are rated critical and 12 are listed by CISA as actively exploited.
CVEs950
Last 12 months74
Critical93
Actively exploited12
All vulnerabilities in the catalogue →⭐ Follow this technology
🔴 Actively exploited (CISA KEV)
| CVE | Severity | EPSS | Active exploitation | Published | Description |
|---|---|---|---|---|---|
| CVE-2026-21385 | High (7.8) | 1.3% | ⚠ Active exploitation | Mar 2, 2026 | Memory corruption while using alignments for memory allocation. |
| CVE-2025-21480 | High (8.6) | 0.46% | ⚠ Active exploitation | Jun 3, 2025 | Memory corruption due to unauthorized command execution in GPU micronode while executing specific sequence of commands. |
| CVE-2025-27038 | High (7.5) | 1.0% | ⚠ Active exploitation | Jun 3, 2025 | Memory corruption while rendering graphics using Adreno GPU drivers in Chrome. |
| CVE-2025-21479 | High (8.6) | 0.84% | ⚠ Active exploitation | Jun 3, 2025 | Memory corruption due to unauthorized command execution in GPU micronode while executing specific sequence of commands. |
| CVE-2024-43047 | High (7.8) | 0.67% | ⚠ Active exploitation | Oct 7, 2024 | Memory corruption while maintaining memory maps of HLOS memory. |
| CVE-2022-22071 | High (7.8) | 0.46% | ⚠ Active exploitation | Jun 14, 2022 | Possible use after free when process shell memory is freed using IOCTL munmap call and process initialization is in progress in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT,… |
| CVE-2023-33063 | High (7.8) | 0.69% | ⚠ Active exploitation | Dec 5, 2023 | Memory corruption in DSP Services during a remote call from HLOS to DSP. |
| CVE-2023-33106 | High (7.8) | 0.92% | ⚠ Active exploitation | Dec 5, 2023 | Memory corruption while submitting a large list of sync points in an AUX command to the IOCTL_KGSL_GPU_AUX_COMMAND. |
| CVE-2023-33107 | High (7.8) | 0.89% | ⚠ Active exploitation | Dec 5, 2023 | Memory corruption in Graphics Linux while assigning shared virtual memory region during IOCTL call. |
| CVE-2020-11261 | High (7.8) | 1.6% | ⚠ Active exploitation | Jun 9, 2021 | Memory corruption due to improper check to return error when user application requests memory allocation of a huge size in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT,… |
| CVE-2021-1906 | Medium (5.5) | 0.52% | ⚠ Active exploitation | May 7, 2021 | 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, Snapdragon Industrial IOT,… |
| CVE-2021-1905 | High (7.8) | 1.5% | ⚠ Active exploitation | May 7, 2021 | 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, Snapdragon Industrial… |
Latest vulnerabilities
| CVE | Severity | EPSS | Active exploitation | Published | Description |
|---|---|---|---|---|---|
| CVE-2026-25275 | High (7.5) | 0.19% | — | Sep 17, 2026 | Transient DOS when processing authentication frames with invalid FILS information element header lengths. |
| CVE-2026-24081 | High (7.4) | 0.10% | — | Sep 17, 2026 | Transient DOS when processing a channel map with insufficient used channels and adaptive frequency hopping is fully enabled. |
| CVE-2026-24075 | High (7) | 0.06% | — | Sep 17, 2026 | Memory Corruption when multiple threads issue concurrent IOCTL requests to the device control handler due to improper synchronization and race conditions. |
| CVE-2026-25292 | High (7.6) | 0.15% | — | Aug 4, 2026 | Memory Corruption when processing untrusted user input in the fastboot command handler for audio framework configuration. |
| CVE-2026-25289 | Critical (9.6) | 0.19% | — | Aug 4, 2026 | Memory Corruption when processing Device Capability Extended attributes in certain NAN Service Discovery Frames with invalid length values. |
| CVE-2026-24084 | High (7.5) | 0.25% | — | Aug 4, 2026 | Weak configuration when UE does not verify the consistency of its additional security capabilities with the replayed capabilities. |
| CVE-2026-24079 | High (8.1) | 0.21% | — | Aug 4, 2026 | Cryptographic Issue while processing registration requests with malformed or missing authentication parameters. |
| CVE-2026-24078 | Medium (6.5) | 0.17% | — | Aug 4, 2026 | Information Disclosure when IPSec negotiation fails or is not established properly during NG-eCall SIP signaling. |
| CVE-2026-24077 | Medium (6.5) | 0.17% | — | Aug 4, 2026 | Information Disclosure when processing wireless network channel switch information with improperly formatted length fields. |
| CVE-2026-24076 | Medium (6.7) | 0.11% | — | Aug 4, 2026 | Memory Corruption when processing registry values with incorrect types using a direct query method. |
| CVE-2026-21379 | High (7.8) | 0.10% | — | Jul 6, 2026 | Memory Corruption when allocating memory with sizes that exceed the maximum allowed value. |
| CVE-2026-25277 | High (8.8) | 0.07% | — | Jun 1, 2026 | Memory corruption while using Strongbox due to buffer overflow. |
| CVE-2026-25276 | High (8.8) | 0.07% | — | Jun 1, 2026 | Memory corruption while using Strongbox due to missing bounds check. |
| CVE-2026-24092 | High (7.2) | 0.10% | — | Jun 1, 2026 | Memory Corruption when processing fastboot commands to set display mode. |
| CVE-2026-24091 | High (7.2) | 0.10% | — | Jun 1, 2026 | Memory corruption while processing fastboot commands with improperly formatted input. |
| CVE-2026-24090 | High (7.1) | 0.06% | — | Jun 1, 2026 | Cryptographic issue while processing partition table entries allows unauthorized modification of boot flow. |
| CVE-2026-24089 | High (7.2) | 0.10% | — | Jun 1, 2026 | Memory corruption while processing fastboot commands with invalid input. |
| CVE-2026-24088 | High (8.2) | 0.07% | — | Jun 1, 2026 | Cryptographic Issue while processing a specific partition which allows unauthorized write access to load a customized bootloader. |
| CVE-2026-24087 | High (7.2) | 0.10% | — | Jun 1, 2026 | Memory corruption while processing fastboot OEM commands. |
| CVE-2026-24085 | High (7.2) | 0.10% | — | Jun 1, 2026 | Memory Corruption when processing display command line information due to improper initialization of a variable. |
| CVE-2025-59611 | Medium (6.7) | 0.08% | — | Jun 1, 2026 | Memory corruption in diagnostic services due to absence of input validation |
| CVE-2025-59610 | Medium (6.4) | 0.06% | — | Jun 1, 2026 | Memory Corruption when processing IOCTL requests with mismatched API versions due to concurrent modification of user-space buffer. |
| CVE-2025-59609 | Medium (5.5) | 0.09% | — | Jun 1, 2026 | Information Disclosure when processing advertisement frames with malformed MBSSID elements of insufficient length. |
| CVE-2025-59605 | High (7.8) | 0.07% | — | Jun 1, 2026 | Memory Corruption when processing device identifier strings that exceed the expected maximum length. |
| CVE-2025-59604 | High (7.8) | 0.07% | — | Jun 1, 2026 | Memory Corruption when running a memory copy operation due to invalid writes caused by a null pointer. |
| CVE-2026-24082 | High (7.8) | 0.07% | — | May 4, 2026 | Memory Corruption when copying data from a freed source while executing performance counter deselect operation. |
| CVE-2025-47407 | High (7) | 0.05% | — | May 4, 2026 | Memory corruption while creating a process on the digital signal processor due to allocation failure at the kernel level. |
| CVE-2025-47404 | High (7.8) | 0.07% | — | May 4, 2026 | Memory corruption when dynamically changing the size of a previously allocated buffer while its contents are being modified. |
| CVE-2025-47403 | High (7.5) | 0.22% | — | May 4, 2026 | Transient DOS when processing a malformed Fast Transition response frame with an invalid header structure during wireless roaming. |
| CVE-2025-47401 | High (7.5) | 0.22% | — | May 4, 2026 | Transient DOS when processing target power rate tables during channel configuration. |
🎯 How it gets exploited (ATT&CK techniques)
Number of CVEs of this technology mapped to each exploitation or primary-impact technique.