Qcn9012 Firmware
by Qualcomm
CVEs (380)
| CVE | Vendor / Product | Sev | Risk | CVSS | EPSS | KEV | Published | Description |
|---|---|---|---|---|---|---|---|---|
| CVE-2022-33252 | Hig | 0.53 | 8.2 | 0.00 | Jan 9, 2023 | Information disclosure due to buffer over-read in WLAN while handling IBSS beacons frame. | ||
| CVE-2022-25746 | Hig | 0.53 | 8.1 | 0.00 | Jan 9, 2023 | Memory corruption in kernel due to missing checks when updating the access rights of a memextent mapping. | ||
| CVE-2022-33268 | Hig | 0.53 | 8.2 | 0.00 | Dec 13, 2022 | Information disclosure due to buffer over-read in Bluetooth HOST while pairing and connecting A2DP. in Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables | ||
| CVE-2022-33235 | Hig | 0.53 | 8.2 | 0.00 | Dec 13, 2022 | Information disclosure due to buffer over-read in WLAN firmware while parsing security context info attributes. in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer Electronics Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT,… | ||
| CVE-2021-30349 | Hig | 0.53 | 8.2 | 0.00 | Jun 14, 2022 | Improper access control sequence for AC database after memory allocation can lead to possible memory corruption in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Voice & Music, Snapdragon Wearables,… | ||
| CVE-2021-35088 | Hig | 0.53 | 8.2 | 0.01 | Apr 1, 2022 | Possible out of bound read due to improper validation of IE length during SSID IE parse when channel is DFS in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Wearables, Snapdragon… | ||
| CVE-2025-59605 | Hig | 0.51 | 7.8 | 0.00 | Jun 1, 2026 | Memory Corruption when processing device identifier strings that exceed the expected maximum length. | ||
| CVE-2025-59604 | Hig | 0.51 | 7.8 | 0.00 | Jun 1, 2026 | Memory Corruption when running a memory copy operation due to invalid writes caused by a null pointer. | ||
| CVE-2026-24082 | Hig | 0.51 | 7.8 | 0.00 | May 4, 2026 | Memory Corruption when copying data from a freed source while executing performance counter deselect operation. | ||
| CVE-2025-47391 | Hig | 0.51 | 7.8 | 0.00 | Apr 6, 2026 | Memory corruption while processing a frame request from user. | ||
| CVE-2025-59600 | Hig | 0.51 | 7.8 | 0.00 | Mar 2, 2026 | Memory Corruption when adding user-supplied data without checking available buffer space. | ||
| CVE-2025-47386 | Hig | 0.51 | 7.8 | 0.00 | Mar 2, 2026 | Memory Corruption while invoking IOCTL calls when concurrent access to shared buffer occurs. | ||
| CVE-2025-47379 | Hig | 0.51 | 7.8 | 0.00 | 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 | Hig | 0.51 | 7.8 | 0.00 | Mar 2, 2026 | Memory Corruption when accessing a buffer after it has been freed while processing IOCTL calls. | ||
| CVE-2025-47376 | Hig | 0.51 | 7.8 | 0.00 | Mar 2, 2026 | Memory Corruption when concurrent access to shared buffer occurs during IOCTL calls. | ||
| CVE-2025-47375 | Hig | 0.51 | 7.8 | 0.00 | Mar 2, 2026 | Memory corruption while handling different IOCTL calls from the user-space simultaneously. | ||
| CVE-2025-47373 | Hig | 0.51 | 7.8 | 0.00 | Mar 2, 2026 | Memory Corruption when accessing buffers with invalid length during TA invocation. | ||
| CVE-2025-47398 | Hig | 0.51 | 7.8 | 0.00 | Feb 2, 2026 | Memory Corruption while deallocating graphics processing unit memory buffers due to improper handling of memory pointers. | ||
| CVE-2025-47397 | Hig | 0.51 | 7.8 | 0.00 | Feb 2, 2026 | Memory Corruption when initiating GPU memory mapping using scatter-gather lists due to unchecked IOMMU mapping errors. | ||
| CVE-2025-47348 | Hig | 0.51 | 7.8 | 0.00 | Jan 7, 2026 | Memory corruption while processing identity credential operations in the trusted application. |
- risk 0.53cvss 8.2epss 0.00
Information disclosure due to buffer over-read in WLAN while handling IBSS beacons frame.
- risk 0.53cvss 8.1epss 0.00
Memory corruption in kernel due to missing checks when updating the access rights of a memextent mapping.
- risk 0.53cvss 8.2epss 0.00
Information disclosure due to buffer over-read in Bluetooth HOST while pairing and connecting A2DP. in Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables
- risk 0.53cvss 8.2epss 0.00
Information disclosure due to buffer over-read in WLAN firmware while parsing security context info attributes. in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer Electronics Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT,…
- risk 0.53cvss 8.2epss 0.00
Improper access control sequence for AC database after memory allocation can lead to possible memory corruption in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Voice & Music, Snapdragon Wearables,…
- risk 0.53cvss 8.2epss 0.01
Possible out of bound read due to improper validation of IE length during SSID IE parse when channel is DFS in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Wearables, Snapdragon…
- risk 0.51cvss 7.8epss 0.00
Memory Corruption when processing device identifier strings that exceed the expected maximum length.
- risk 0.51cvss 7.8epss 0.00
Memory Corruption when running a memory copy operation due to invalid writes caused by a null pointer.
- risk 0.51cvss 7.8epss 0.00
Memory Corruption when copying data from a freed source while executing performance counter deselect operation.
- risk 0.51cvss 7.8epss 0.00
Memory corruption while processing a frame request from user.
- risk 0.51cvss 7.8epss 0.00
Memory Corruption when adding user-supplied data without checking available buffer space.
- risk 0.51cvss 7.8epss 0.00
Memory Corruption while invoking IOCTL calls when concurrent access to shared buffer occurs.
- risk 0.51cvss 7.8epss 0.00
Memory Corruption when concurrent access to shared buffer occurs due to improper synchronization between assignment and deallocation of buffer resources.
- risk 0.51cvss 7.8epss 0.00
Memory Corruption when accessing a buffer after it has been freed while processing IOCTL calls.
- risk 0.51cvss 7.8epss 0.00
Memory Corruption when concurrent access to shared buffer occurs during IOCTL calls.
- risk 0.51cvss 7.8epss 0.00
Memory corruption while handling different IOCTL calls from the user-space simultaneously.
- risk 0.51cvss 7.8epss 0.00
Memory Corruption when accessing buffers with invalid length during TA invocation.
- risk 0.51cvss 7.8epss 0.00
Memory Corruption while deallocating graphics processing unit memory buffers due to improper handling of memory pointers.
- risk 0.51cvss 7.8epss 0.00
Memory Corruption when initiating GPU memory mapping using scatter-gather lists due to unchecked IOMMU mapping errors.
- risk 0.51cvss 7.8epss 0.00
Memory corruption while processing identity credential operations in the trusted application.
Page 7 of 19