Qualcomm
Qualcomm Wcn3910 Firmware: vulnerabilities and CVEs
Qualcomm Wcn3910 Firmware has 520 published vulnerabilities, 44 of them in the last 12 months. 75 are rated critical and 8 are listed by CISA as actively exploited.
CVEs520
Last 12 months44
Critical75
Actively exploited8
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-2023-33063 | High (7.8) | 0.57% | ⚠ 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.75% | ⚠ 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.72% | ⚠ Active exploitation | Dec 5, 2023 | Memory corruption in Graphics Linux while assigning shared virtual memory region during IOCTL call. |
| 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-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-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-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-21369 | Medium (5.3) | 0.08% | — | Jul 6, 2026 | Memory Corruption when handling flash commands due to outdated LED count values being used after userspace modification. |
| 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-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-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-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-47392 | High (8.8) | 0.17% | — | Apr 6, 2026 | Memory corruption when decoding corrupted satellite data files with invalid signature offsets. |
| CVE-2025-47389 | High (7.8) | 0.10% | — | Apr 6, 2026 | Memory corruption when buffer copy operation fails due to integer overflow during attestation report generation. |
| CVE-2026-21385 | High (7.8) | 1.3% | ⚠ Active exploitation | Mar 2, 2026 | Memory corruption while using alignments for memory allocation. |
| CVE-2025-59600 | High (7.8) | 0.07% | — | Mar 2, 2026 | Memory Corruption when adding user-supplied data without checking available buffer space. |
| CVE-2025-47386 | High (7.8) | 0.07% | — | Mar 2, 2026 | Memory Corruption while invoking IOCTL calls when concurrent access to shared buffer occurs. |
| CVE-2025-47383 | High (7.2) | 0.14% | — | Mar 2, 2026 | Weak configuration may lead to cryptographic issue when a VoWiFi call is triggered from UE. |
| CVE-2025-47379 | High (7.8) | 0.07% | — | Mar 2, 2026 | Memory Corruption when concurrent access to shared buffer occurs due to improper synchronization between assignment and deallocation of buffer resources. |
| CVE-2025-47377 | High (7.8) | 0.07% | — | Mar 2, 2026 | Memory Corruption when accessing a buffer after it has been freed while processing IOCTL calls. |
| CVE-2025-47376 | High (7.8) | 0.07% | — | Mar 2, 2026 | Memory Corruption when concurrent access to shared buffer occurs during IOCTL calls. |
| CVE-2025-47375 | High (7.8) | 0.07% | — | Mar 2, 2026 | Memory corruption while handling different IOCTL calls from the user-space simultaneously. |
| CVE-2025-47373 | High (7.8) | 0.07% | — | Mar 2, 2026 | Memory Corruption when accessing buffers with invalid length during TA invocation. |
| CVE-2025-47371 | Medium (6.5) | 0.11% | — | Mar 2, 2026 | Transient DOS when an LTE RLC packet with invalid TB is received by UE. |
🎯 How it gets exploited (ATT&CK techniques)
Number of CVEs of this technology mapped to each exploitation or primary-impact technique.