Snapdragon 460 Mobile Platform Firmware
by Qualcomm
CVEs (204)
| CVE | Vendor / Product | Sev | Risk | CVSS | EPSS | KEV | Published | Description |
|---|---|---|---|---|---|---|---|---|
| CVE-2025-21479 | Hig | 0.68 | 8.6 | 0.01 | KEV | Jun 3, 2025 | Memory corruption due to unauthorized command execution in GPU micronode while executing specific sequence of commands. | |
| CVE-2025-21480 | Hig | 0.68 | 8.6 | 0.00 | KEV | Jun 3, 2025 | Memory corruption due to unauthorized command execution in GPU micronode while executing specific sequence of commands. | |
| 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-21483 | Cri | 0.64 | 9.8 | 0.00 | Sep 24, 2025 | Memory corruption when the UE receives an RTP packet from the network, during the reassembly of NALUs. | ||
| CVE-2023-22388 | Cri | 0.64 | 9.8 | 0.00 | Nov 7, 2023 | Memory Corruption in Multi-mode Call Processor while processing bit mask API. | ||
| CVE-2026-21385 | Hig | 0.63 | 7.8 | 0.01 | KEV | Mar 2, 2026 | Memory corruption while using alignments for memory allocation. | |
| CVE-2023-28578 | Cri | 0.60 | 9.3 | 0.00 | Mar 4, 2024 | Memory corruption in Core Services while executing the command for removing a single event listener. | ||
| CVE-2023-33072 | Cri | 0.60 | 9.3 | 0.00 | Feb 6, 2024 | Memory corruption in Core while processing control functions. | ||
| CVE-2023-33030 | Cri | 0.60 | 9.3 | 0.00 | Jan 2, 2024 | Memory corruption in HLOS while running playready use-case. | ||
| CVE-2023-43551 | Cri | 0.59 | 9.1 | 0.00 | Jun 3, 2024 | Cryptographic issue while performing attach with a LTE network, a rogue base station can skip the authentication phase and immediately send the Security Mode Command. | ||
| CVE-2026-25277 | Hig | 0.57 | 8.8 | 0.00 | Jun 1, 2026 | Memory corruption while using Strongbox due to buffer overflow. | ||
| CVE-2026-25276 | Hig | 0.57 | 8.8 | 0.00 | Jun 1, 2026 | Memory corruption while using Strongbox due to missing bounds check. | ||
| CVE-2025-47392 | Hig | 0.57 | 8.8 | 0.00 | Apr 6, 2026 | Memory corruption when decoding corrupted satellite data files with invalid signature offsets. | ||
| 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-33060 | Hig | 0.55 | 8.4 | 0.00 | Sep 2, 2024 | Memory corruption when two threads try to map and unmap a single node simultaneously. | ||
| 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-33023 | Hig | 0.55 | 8.4 | 0.00 | Aug 5, 2024 | Memory corruption while creating a fence to wait on timeline events, and simultaneously signal timeline events. |
- risk 0.68cvss 8.6epss 0.01
Memory corruption due to unauthorized command execution in GPU micronode while executing specific sequence of commands.
- risk 0.68cvss 8.6epss 0.00
Memory corruption due to unauthorized command execution in GPU micronode while executing specific sequence of commands.
- 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 when the UE receives an RTP packet from the network, during the reassembly of NALUs.
- risk 0.64cvss 9.8epss 0.00
Memory Corruption in Multi-mode Call Processor while processing bit mask API.
- risk 0.63cvss 7.8epss 0.01
Memory corruption while using alignments for memory allocation.
- risk 0.60cvss 9.3epss 0.00
Memory corruption in Core Services while executing the command for removing a single event listener.
- risk 0.60cvss 9.3epss 0.00
Memory corruption in Core while processing control functions.
- risk 0.60cvss 9.3epss 0.00
Memory corruption in HLOS while running playready use-case.
- risk 0.59cvss 9.1epss 0.00
Cryptographic issue while performing attach with a LTE network, a rogue base station can skip the authentication phase and immediately send the Security Mode Command.
- risk 0.57cvss 8.8epss 0.00
Memory corruption while using Strongbox due to buffer overflow.
- risk 0.57cvss 8.8epss 0.00
Memory corruption while using Strongbox due to missing bounds check.
- risk 0.57cvss 8.8epss 0.00
Memory corruption when decoding corrupted satellite data files with invalid signature offsets.
- 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 two threads try to map and unmap a single node simultaneously.
- 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 while creating a fence to wait on timeline events, and simultaneously signal timeline events.
Page 1 of 11