Qualcomm
Qualcomm Wcd9341 Firmware: vulnerabilities and CVEs
Qualcomm Wcd9341 Firmware has 813 published vulnerabilities, 37 of them in the last 12 months. 71 are rated critical and 11 are listed by CISA as actively exploited.
CVEs813
Last 12 months37
Critical71
Actively exploited11
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-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-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-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-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-24091 | High (7.2) | 0.10% | — | Jun 1, 2026 | Memory corruption while processing fastboot commands with improperly formatted input. |
| 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-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-2026-21378 | High (7.8) | 0.07% | — | Apr 6, 2026 | Memory Corruption when accessing an output buffer without validating its size during IOCTL processing in a camera sensor driver. |
| CVE-2026-21376 | High (7.8) | 0.10% | — | Apr 6, 2026 | Memory Corruption when accessing an output buffer without validating its size during IOCTL processing in a camera sensor driver. |
| CVE-2026-21374 | High (7.8) | 0.11% | — | Apr 6, 2026 | Memory Corruption when processing auxiliary sensor input/output control commands with insufficient buffer size validation. |
| CVE-2026-21373 | High (7.8) | 0.08% | — | Apr 6, 2026 | Memory Corruption when accessing an output buffer without validating its size during IOCTL processing. |
| CVE-2026-21371 | High (7.8) | 0.10% | — | Apr 6, 2026 | Memory Corruption when retrieving output buffer with insufficient size validation. |
| CVE-2025-47392 | High (8.8) | 0.17% | — | Apr 6, 2026 | Memory corruption when decoding corrupted satellite data files with invalid signature offsets. |
| CVE-2026-21385 | High (7.8) | 1.3% | ⚠ Active exploitation | Mar 2, 2026 | Memory corruption while using alignments for memory allocation. |
| 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-47384 | Medium (6.5) | 0.11% | — | Mar 2, 2026 | Transient DOS when MAC configures config id greater than supported maximum value. |
| 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-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-47371 | Medium (6.5) | 0.11% | — | Mar 2, 2026 | Transient DOS when an LTE RLC packet with invalid TB is received by UE. |
| CVE-2025-47398 | High (7.8) | 0.11% | — | Feb 2, 2026 | Memory Corruption while deallocating graphics processing unit memory buffers due to improper handling of memory pointers. |
| CVE-2025-47359 | High (7.8) | 0.10% | — | Feb 2, 2026 | Memory Corruption when multiple threads simultaneously access a memory free API. |
| CVE-2025-47369 | Medium (5.5) | 0.08% | — | Jan 7, 2026 | Information disclosure when a weak hashed value is returned to userland code in response to a IOCTL call to obtain a session ID. |
| CVE-2025-47348 | High (7.8) | 0.08% | — | Jan 7, 2026 | Memory corruption while processing identity credential operations in the trusted application. |
| CVE-2025-47333 | Medium (6.6) | 0.08% | — | Jan 7, 2026 | Memory corruption while handling buffer mapping operations in the cryptographic driver. |
🎯 How it gets exploited (ATT&CK techniques)
Number of CVEs of this technology mapped to each exploitation or primary-impact technique.