Qcm6490 Firmware
by Qualcomm
CVEs (793)
| CVE | Vendor / Product | Sev | Risk | CVSS | EPSS | KEV | Published | Description |
|---|---|---|---|---|---|---|---|---|
| CVE-2020-11191 | Hig | 0.53 | 8.2 | 0.01 | Apr 7, 2021 | Out of bound read occurs while processing crafted SDP due to lack of check of null string in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer Electronics Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon IoT, Snapdragon… | ||
| CVE-2021-1906 | Med | 0.52 | 6.2 | 0.01 | KEV | 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, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon… | |
| CVE-2026-57559 | Hig | 0.51 | 7.8 | 0.00 | Oct 6, 2026 | Memory corruption while processing service requests. | ||
| CVE-2026-57555 | Hig | 0.51 | 7.8 | 0.00 | Oct 6, 2026 | Memory Corruption when executing system service routines due to improper handling of user input buffers. | ||
| CVE-2026-57554 | Hig | 0.51 | 7.8 | 0.00 | Oct 6, 2026 | Memory Corruption when asynchronous threads access shared performance counter data simultaneously during FastRPC invocations. | ||
| CVE-2026-57545 | Hig | 0.51 | 7.8 | 0.00 | Oct 6, 2026 | Memory corruption when processing draw objects of incorrect type during graphics command list execution. | ||
| CVE-2026-25291 | Hig | 0.51 | 7.8 | 0.00 | Oct 6, 2026 | Memory corruption when performing concurrent operations on shared memory page lists due to lack of proper synchronization mechanisms. | ||
| CVE-2026-25267 | Hig | 0.51 | 7.8 | 0.00 | Oct 6, 2026 | Memory corruption when non-secure loader rewrites page tables before secure memory initialization. | ||
| CVE-2026-25280 | Hig | 0.51 | 7.8 | 0.00 | Sep 17, 2026 | Memory corruption when processing escape handling flow with insufficient user buffer sizes. | ||
| CVE-2026-24075 | Hig | 0.51 | 7.8 | 0.00 | 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-24074 | Hig | 0.51 | 7.8 | 0.00 | Sep 17, 2026 | Memory Corruption when processing data with large offset and length values exceeds buffer limits during data copy operations. | ||
| CVE-2026-25260 | Hig | 0.51 | 7.8 | 0.00 | Jun 1, 2026 | Memory Corruption when accessing shared buffers without validation of concurrent user-mode input modifications. | ||
| CVE-2026-25259 | Hig | 0.51 | 7.8 | 0.00 | Jun 1, 2026 | Memory corruption while processing multiple IOCTL command for escape operations. | ||
| CVE-2025-59606 | Hig | 0.51 | 7.8 | 0.00 | Jun 1, 2026 | Memory Corruption when writing to invalid memory locations occurs due to heap memory exhaustion during secure data initialization. | ||
| 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-2026-21378 | Hig | 0.51 | 7.8 | 0.00 | 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 | Hig | 0.51 | 7.8 | 0.00 | Apr 6, 2026 | Memory Corruption when accessing an output buffer without validating its size during IOCTL processing in a camera sensor driver. | ||
| CVE-2026-21375 | Hig | 0.51 | 7.8 | 0.00 | Apr 6, 2026 | Memory Corruption when accessing an output buffer without validating its size during IOCTL processing. |
- risk 0.53cvss 8.2epss 0.01
Out of bound read occurs while processing crafted SDP due to lack of check of null string in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer Electronics Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon IoT, Snapdragon…
- risk 0.52cvss 6.2epss 0.01
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, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon…
- risk 0.51cvss 7.8epss 0.00
Memory corruption while processing service requests.
- risk 0.51cvss 7.8epss 0.00
Memory Corruption when executing system service routines due to improper handling of user input buffers.
- risk 0.51cvss 7.8epss 0.00
Memory Corruption when asynchronous threads access shared performance counter data simultaneously during FastRPC invocations.
- risk 0.51cvss 7.8epss 0.00
Memory corruption when processing draw objects of incorrect type during graphics command list execution.
- risk 0.51cvss 7.8epss 0.00
Memory corruption when performing concurrent operations on shared memory page lists due to lack of proper synchronization mechanisms.
- risk 0.51cvss 7.8epss 0.00
Memory corruption when non-secure loader rewrites page tables before secure memory initialization.
- risk 0.51cvss 7.8epss 0.00
Memory corruption when processing escape handling flow with insufficient user buffer sizes.
- risk 0.51cvss 7.8epss 0.00
Memory Corruption when multiple threads issue concurrent IOCTL requests to the device control handler due to improper synchronization and race conditions.
- risk 0.51cvss 7.8epss 0.00
Memory Corruption when processing data with large offset and length values exceeds buffer limits during data copy operations.
- risk 0.51cvss 7.8epss 0.00
Memory Corruption when accessing shared buffers without validation of concurrent user-mode input modifications.
- risk 0.51cvss 7.8epss 0.00
Memory corruption while processing multiple IOCTL command for escape operations.
- risk 0.51cvss 7.8epss 0.00
Memory Corruption when writing to invalid memory locations occurs due to heap memory exhaustion during secure data initialization.
- 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 when accessing an output buffer without validating its size during IOCTL processing in a camera sensor driver.
- risk 0.51cvss 7.8epss 0.00
Memory Corruption when accessing an output buffer without validating its size during IOCTL processing in a camera sensor driver.
- risk 0.51cvss 7.8epss 0.00
Memory Corruption when accessing an output buffer without validating its size during IOCTL processing.
Page 14 of 40