Qcs6490 Firmware
by Qualcomm
CVEs (320)
| CVE | Vendor / Product | Sev | Risk | CVSS | EPSS | KEV | Published | Description |
|---|---|---|---|---|---|---|---|---|
| CVE-2023-28540 | Cri | 0.59 | 9.1 | 0.00 | Oct 3, 2023 | Cryptographic issue in Data Modem due to improper authentication during TLS handshake. | ||
| CVE-2021-30343 | Cri | 0.59 | 9.1 | 0.00 | Jun 14, 2022 | Improper integrity check can lead to race condition between tasks PDCP and RRC? after a valid RRC Command packet has been received in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Industrial IOT, Snapdragon Mobile | ||
| CVE-2021-30339 | Cri | 0.59 | 9.0 | 0.00 | Jun 14, 2022 | Reading PRNG output may lead to improper key generation due to lack of buffer validation in Snapdragon Connectivity, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Wearables, Snapdragon Wired Infrastructure and Networking | ||
| CVE-2021-1924 | Cri | 0.59 | 9.0 | 0.00 | Nov 12, 2021 | Information disclosure through timing and power side-channels during mod exponentiation for RSA-CRT in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer Electronics Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon IoT,… | ||
| CVE-2023-21673 | Hig | 0.57 | 8.7 | 0.00 | Oct 3, 2023 | Improper Access to the VM resource manager can lead to Memory Corruption. | ||
| CVE-2025-47345 | Hig | 0.55 | 8.4 | 0.00 | Jan 7, 2026 | Cryptographic issue may occur while encrypting license data. | ||
| CVE-2024-33056 | Hig | 0.55 | 8.4 | 0.00 | Dec 2, 2024 | Memory corruption when allocating and accessing an entry in an SMEM partition continuously. | ||
| CVE-2024-33047 | Hig | 0.55 | 8.4 | 0.00 | Sep 2, 2024 | Memory corruption when the captureRead QDCM command is invoked from user-space. | ||
| CVE-2024-33035 | Hig | 0.55 | 8.4 | 0.00 | Sep 2, 2024 | Memory corruption while calculating total metadata size when a very high reserved size is requested by gralloc clients. | ||
| CVE-2024-33034 | Hig | 0.55 | 8.4 | 0.00 | Aug 5, 2024 | Memory corruption can occur if VBOs hold outdated or invalid GPU SMMU mappings, especially when the binding and reclaiming of memory buffers are performed at the same time. | ||
| CVE-2024-33028 | Hig | 0.55 | 8.4 | 0.00 | Aug 5, 2024 | Memory corruption as fence object may still be accessed in timeline destruct after isync fence is released. | ||
| CVE-2024-23383 | Hig | 0.55 | 8.4 | 0.00 | Aug 5, 2024 | Memory corruption when kernel driver attempts to trigger hardware fences. | ||
| CVE-2024-23381 | Hig | 0.55 | 8.4 | 0.00 | Aug 5, 2024 | Memory corruption when memory mapped in a VBO is not unmapped by the GPU SMMU. | ||
| CVE-2024-23373 | Hig | 0.55 | 8.4 | 0.00 | Jul 1, 2024 | Memory corruption when IOMMU unmap operation fails, the DMA and anon buffers are getting released. | ||
| CVE-2024-23372 | Hig | 0.55 | 8.4 | 0.00 | Jul 1, 2024 | Memory corruption while invoking IOCTL call for GPU memory allocation and size param is greater than expected size. | ||
| CVE-2023-43554 | Hig | 0.55 | 8.4 | 0.00 | Jul 1, 2024 | Memory corruption while processing IOCTL handler in FastRPC. | ||
| CVE-2024-23351 | Hig | 0.55 | 8.4 | 0.00 | May 6, 2024 | Memory corruption as GPU registers beyond the last protected range can be accessed through LPAC submissions. | ||
| CVE-2024-21471 | Hig | 0.55 | 8.4 | 0.00 | May 6, 2024 | Memory corruption when IOMMU unmap of a GPU buffer fails in Linux. | ||
| CVE-2023-43531 | Hig | 0.55 | 8.4 | 0.00 | May 6, 2024 | Memory corruption while verifying the serialized header when the key pairs are generated. | ||
| CVE-2024-21468 | Hig | 0.55 | 8.4 | 0.00 | Apr 1, 2024 | Memory corruption when there is failed unmap operation in GPU. |
- risk 0.59cvss 9.1epss 0.00
Cryptographic issue in Data Modem due to improper authentication during TLS handshake.
- risk 0.59cvss 9.1epss 0.00
Improper integrity check can lead to race condition between tasks PDCP and RRC? after a valid RRC Command packet has been received in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Industrial IOT, Snapdragon Mobile
- risk 0.59cvss 9.0epss 0.00
Reading PRNG output may lead to improper key generation due to lack of buffer validation in Snapdragon Connectivity, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Wearables, Snapdragon Wired Infrastructure and Networking
- risk 0.59cvss 9.0epss 0.00
Information disclosure through timing and power side-channels during mod exponentiation for RSA-CRT in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer Electronics Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon IoT,…
- risk 0.57cvss 8.7epss 0.00
Improper Access to the VM resource manager can lead to Memory Corruption.
- risk 0.55cvss 8.4epss 0.00
Cryptographic issue may occur while encrypting license data.
- risk 0.55cvss 8.4epss 0.00
Memory corruption when allocating and accessing an entry in an SMEM partition continuously.
- risk 0.55cvss 8.4epss 0.00
Memory corruption when the captureRead QDCM command is invoked from user-space.
- risk 0.55cvss 8.4epss 0.00
Memory corruption while calculating total metadata size when a very high reserved size is requested by gralloc clients.
- risk 0.55cvss 8.4epss 0.00
Memory corruption can occur if VBOs hold outdated or invalid GPU SMMU mappings, especially when the binding and reclaiming of memory buffers are performed at the same time.
- risk 0.55cvss 8.4epss 0.00
Memory corruption as fence object may still be accessed in timeline destruct after isync fence is released.
- risk 0.55cvss 8.4epss 0.00
Memory corruption when kernel driver attempts to trigger hardware fences.
- risk 0.55cvss 8.4epss 0.00
Memory corruption when memory mapped in a VBO is not unmapped by the GPU SMMU.
- risk 0.55cvss 8.4epss 0.00
Memory corruption when IOMMU unmap operation fails, the DMA and anon buffers are getting released.
- risk 0.55cvss 8.4epss 0.00
Memory corruption while invoking IOCTL call for GPU memory allocation and size param is greater than expected size.
- risk 0.55cvss 8.4epss 0.00
Memory corruption while processing IOCTL handler in FastRPC.
- risk 0.55cvss 8.4epss 0.00
Memory corruption as GPU registers beyond the last protected range can be accessed through LPAC submissions.
- risk 0.55cvss 8.4epss 0.00
Memory corruption when IOMMU unmap of a GPU buffer fails in Linux.
- risk 0.55cvss 8.4epss 0.00
Memory corruption while verifying the serialized header when the key pairs are generated.
- risk 0.55cvss 8.4epss 0.00
Memory corruption when there is failed unmap operation in GPU.
Page 2 of 16