Qcs5430 Firmware
by Qualcomm
CVEs (137)
| CVE | Vendor / Product | Sev | Risk | CVSS | EPSS | KEV | Published | Description |
|---|---|---|---|---|---|---|---|---|
| CVE-2023-33107 | Hig | 0.67 | 8.4 | 0.01 | KEV | Dec 5, 2023 | Memory corruption in Graphics Linux while assigning shared virtual memory region during IOCTL call. | |
| CVE-2023-33106 | Hig | 0.67 | 8.4 | 0.01 | KEV | 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-2025-27034 | Cri | 0.64 | 9.8 | 0.00 | Sep 24, 2025 | Memory corruption while selecting the PLMN from SOR failed list. | ||
| CVE-2023-43556 | Cri | 0.60 | 9.3 | 0.00 | Jun 3, 2024 | Memory corruption in Hypervisor when platform information mentioned is not aligned. | ||
| CVE-2025-21450 | Cri | 0.59 | 9.1 | 0.00 | Jul 8, 2025 | Cryptographic issue occurs due to use of insecure connection method while downloading. | ||
| CVE-2023-33054 | Cri | 0.59 | 9.1 | 0.00 | Dec 5, 2023 | Cryptographic issue in GPS HLOS Driver while downloading Qualcomm GNSS assistance data. | ||
| 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-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.67cvss 8.4epss 0.01
Memory corruption in Graphics Linux while assigning shared virtual memory region during IOCTL call.
- risk 0.67cvss 8.4epss 0.01
Memory corruption while submitting a large list of sync points in an AUX command to the IOCTL_KGSL_GPU_AUX_COMMAND.
- risk 0.64cvss 9.8epss 0.00
Memory corruption while selecting the PLMN from SOR failed list.
- risk 0.60cvss 9.3epss 0.00
Memory corruption in Hypervisor when platform information mentioned is not aligned.
- risk 0.59cvss 9.1epss 0.00
Cryptographic issue occurs due to use of insecure connection method while downloading.
- risk 0.59cvss 9.1epss 0.00
Cryptographic issue in GPS HLOS Driver while downloading Qualcomm GNSS assistance data.
- 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 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 1 of 7