Qualcomm
Qualcomm Sa6150p Firmware: vulnerabilities and CVEs
Qualcomm Sa6150p Firmware has 596 published vulnerabilities, 43 of them in the last 12 months. 45 are rated critical and 7 are listed by CISA as actively exploited.
CVEs596
Last 12 months43
Critical45
Actively exploited7
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-2024-43047 | High (7.8) | 0.67% | ⚠ Active exploitation | Oct 7, 2024 | Memory corruption while maintaining memory maps of HLOS memory. |
| 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-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-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-24080 | High (7.8) | 0.10% | — | Aug 4, 2026 | Memory Corruption when handling malformed request parameters in the fingerprint TA. |
| CVE-2026-21366 | High (7.8) | 0.10% | — | Aug 4, 2026 | Memory corruption while processing a packet with a size close to 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-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-59606 | High (7.8) | 0.07% | — | Jun 1, 2026 | Memory Corruption when writing to invalid memory locations occurs due to heap memory exhaustion during secure data initialization. |
| 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-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-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-47373 | High (7.8) | 0.07% | — | Mar 2, 2026 | Memory Corruption when accessing buffers with invalid length during TA invocation. |
| CVE-2025-47366 | High (7.8) | 0.10% | — | Feb 2, 2026 | Cryptographic issue when a Trusted Zone with outdated code is triggered by a HLOS providing incorrect input. |
| CVE-2025-47364 | High (7.8) | 0.10% | — | Feb 2, 2026 | Memory corruption while calculating offset from partition start point. |
| CVE-2025-47363 | High (7.8) | 0.10% | — | Feb 2, 2026 | Memory corruption when calculating oversized partition sizes without proper checks. |
| 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-47346 | High (7.8) | 0.08% | — | Jan 7, 2026 | Memory corruption while processing a secure logging command in the trusted application. |
| CVE-2025-47339 | High (7.8) | 0.08% | — | Jan 7, 2026 | Memory corruption while deinitializing a HDCP session. |
| CVE-2025-47333 | Medium (6.6) | 0.08% | — | Jan 7, 2026 | Memory corruption while handling buffer mapping operations in the cryptographic driver. |
| CVE-2025-47331 | Medium (6.1) | 0.08% | — | Jan 7, 2026 | Information disclosure while processing a firmware event. |
| CVE-2025-47330 | Medium (5.5) | 0.07% | — | Jan 7, 2026 | Transient DOS while parsing video packets received from the video firmware. |
🎯 How it gets exploited (ATT&CK techniques)
Number of CVEs of this technology mapped to each exploitation or primary-impact technique.