Qca6391 Firmware
by Qualcomm
CVEs (960)
| CVE | Vendor / Product | Sev | Risk | CVSS | EPSS | KEV | Published | Description |
|---|---|---|---|---|---|---|---|---|
| CVE-2020-11262 | Hig | 0.46 | 7.0 | 0.00 | Jun 9, 2021 | A race between command submission and destroying the context can cause an invalid context being added to the list leads to use after free issue. in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon… | ||
| CVE-2020-11250 | Hig | 0.46 | 7.0 | 0.00 | Jun 9, 2021 | Use after free due to race condition when reopening the device driver repeatedly in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables, Snapdragon… | ||
| CVE-2020-11161 | Hig | 0.46 | 7.1 | 0.00 | Jun 9, 2021 | Out-of-bounds memory access can occur while calculating alignment requirements for a negative width from external components in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice &… | ||
| CVE-2020-11290 | Hig | 0.46 | 7.0 | 0.00 | Mar 17, 2021 | Use after free condition in msm ioctl events due to race between the ioctl register and deregister events in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Wearables | ||
| CVE-2020-11203 | Hig | 0.46 | 7.1 | 0.00 | Feb 22, 2021 | Stack overflow may occur if GSM/WCDMA broadcast config size received from user is larger than variable length array in Snapdragon Auto, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Wearables | ||
| CVE-2026-25274 | Med | 0.44 | 6.7 | 0.00 | Oct 6, 2026 | Memory Corruption when processing concurrent DMA buffer allocation and deallocation commands without proper synchronization. | ||
| CVE-2026-25272 | Med | 0.44 | 6.7 | 0.00 | Oct 6, 2026 | Memory Corruption when processing camera CRE driver operations with improper handling of buffer limits during hardware update preparation. | ||
| CVE-2026-25270 | Med | 0.44 | 6.7 | 0.00 | Oct 6, 2026 | Memory corruption when processing command buffer requests with invalid length parameters in the Android Camera driver. | ||
| CVE-2026-25269 | Med | 0.44 | 6.7 | 0.00 | Oct 6, 2026 | Memory corruption when processing camera requests with excessive batch and IO buffer configurations exceeds allocated memory size. | ||
| CVE-2026-24076 | Med | 0.44 | 6.7 | 0.00 | Aug 4, 2026 | Memory Corruption when processing registry values with incorrect types using a direct query method. | ||
| CVE-2025-59611 | Med | 0.44 | 6.7 | 0.00 | Jun 1, 2026 | Memory corruption in diagnostic services due to absence of input validation | ||
| CVE-2025-47337 | Med | 0.44 | 6.7 | 0.00 | Jan 7, 2026 | Memory corruption while accessing a synchronization object during concurrent operations. | ||
| CVE-2025-47334 | Med | 0.44 | 6.7 | 0.00 | Jan 7, 2026 | Memory corruption while processing shared command buffer packet between camera userspace and kernel. | ||
| CVE-2024-49848 | Med | 0.44 | 6.7 | 0.00 | Apr 7, 2025 | Memory corruption while processing multiple IOCTL calls from HLOS to DSP. | ||
| CVE-2024-33053 | Med | 0.44 | 6.7 | 0.00 | Dec 2, 2024 | Memory corruption when multiple threads try to unregister the CVP buffer at the same time. | ||
| CVE-2024-33040 | Med | 0.44 | 6.7 | 0.00 | Dec 2, 2024 | Memory corruption while invoking redundant release command to release one buffer from user space as race condition can occur in kernel space between buffer release and buffer access. | ||
| CVE-2024-33036 | Med | 0.44 | 6.7 | 0.00 | Dec 2, 2024 | Memory corruption while parsing sensor packets in camera driver, user-space variable is used while allocating memory in kernel and parsing which can lead to huge allocation or invalid memory access. | ||
| CVE-2021-30299 | Med | 0.44 | 6.7 | 0.00 | Nov 22, 2024 | Possible out of bound access in audio module due to lack of validation of user provided input. | ||
| CVE-2024-33032 | Med | 0.44 | 6.7 | 0.00 | Nov 4, 2024 | Memory corruption when the user application modifies the same shared memory asynchronously when kernel is accessing it. | ||
| CVE-2024-23377 | Med | 0.44 | 6.7 | 0.00 | Nov 4, 2024 | Memory corruption while invoking IOCTL command from user-space, when a user modifies the original packet size of the command after system properties have been already sent to the EVA driver. |
- risk 0.46cvss 7.0epss 0.00
A race between command submission and destroying the context can cause an invalid context being added to the list leads to use after free issue. in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon…
- risk 0.46cvss 7.0epss 0.00
Use after free due to race condition when reopening the device driver repeatedly in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables, Snapdragon…
- risk 0.46cvss 7.1epss 0.00
Out-of-bounds memory access can occur while calculating alignment requirements for a negative width from external components in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice &…
- risk 0.46cvss 7.0epss 0.00
Use after free condition in msm ioctl events due to race between the ioctl register and deregister events in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Wearables
- risk 0.46cvss 7.1epss 0.00
Stack overflow may occur if GSM/WCDMA broadcast config size received from user is larger than variable length array in Snapdragon Auto, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Wearables
- risk 0.44cvss 6.7epss 0.00
Memory Corruption when processing concurrent DMA buffer allocation and deallocation commands without proper synchronization.
- risk 0.44cvss 6.7epss 0.00
Memory Corruption when processing camera CRE driver operations with improper handling of buffer limits during hardware update preparation.
- risk 0.44cvss 6.7epss 0.00
Memory corruption when processing command buffer requests with invalid length parameters in the Android Camera driver.
- risk 0.44cvss 6.7epss 0.00
Memory corruption when processing camera requests with excessive batch and IO buffer configurations exceeds allocated memory size.
- risk 0.44cvss 6.7epss 0.00
Memory Corruption when processing registry values with incorrect types using a direct query method.
- risk 0.44cvss 6.7epss 0.00
Memory corruption in diagnostic services due to absence of input validation
- risk 0.44cvss 6.7epss 0.00
Memory corruption while accessing a synchronization object during concurrent operations.
- risk 0.44cvss 6.7epss 0.00
Memory corruption while processing shared command buffer packet between camera userspace and kernel.
- risk 0.44cvss 6.7epss 0.00
Memory corruption while processing multiple IOCTL calls from HLOS to DSP.
- risk 0.44cvss 6.7epss 0.00
Memory corruption when multiple threads try to unregister the CVP buffer at the same time.
- risk 0.44cvss 6.7epss 0.00
Memory corruption while invoking redundant release command to release one buffer from user space as race condition can occur in kernel space between buffer release and buffer access.
- risk 0.44cvss 6.7epss 0.00
Memory corruption while parsing sensor packets in camera driver, user-space variable is used while allocating memory in kernel and parsing which can lead to huge allocation or invalid memory access.
- risk 0.44cvss 6.7epss 0.00
Possible out of bound access in audio module due to lack of validation of user provided input.
- risk 0.44cvss 6.7epss 0.00
Memory corruption when the user application modifies the same shared memory asynchronously when kernel is accessing it.
- risk 0.44cvss 6.7epss 0.00
Memory corruption while invoking IOCTL command from user-space, when a user modifies the original packet size of the command after system properties have been already sent to the EVA driver.
Page 39 of 48