Sa8295p Firmware
by Qualcomm
CVEs (478)
| CVE | Vendor / Product | Sev | Risk | CVSS | EPSS | KEV | Published | Description |
|---|---|---|---|---|---|---|---|---|
| CVE-2022-33288 | Cri | 0.60 | 9.3 | 0.00 | Apr 13, 2023 | Memory corruption due to buffer copy without checking the size of input in Core while sending SCM command to get write protection information. | ||
| CVE-2022-33269 | Cri | 0.60 | 9.3 | 0.00 | Apr 13, 2023 | Memory corruption due to integer overflow or wraparound in Core while DDR memory assignment. | ||
| CVE-2022-33231 | Cri | 0.60 | 9.3 | 0.00 | Apr 13, 2023 | Memory corruption due to double free in core while initializing the encryption key. | ||
| CVE-2022-33257 | Cri | 0.60 | 9.3 | 0.00 | Mar 10, 2023 | Memory corruption in Core due to time-of-check time-of-use race condition during dump collection in trust zone. | ||
| CVE-2022-33232 | Cri | 0.60 | 9.3 | 0.00 | Feb 12, 2023 | Memory corruption due to buffer copy without checking size of input while running memory sharing tests with large scattered memory. | ||
| CVE-2022-33219 | Cri | 0.60 | 9.3 | 0.00 | Jan 9, 2023 | Memory corruption in Automotive due to integer overflow to buffer overflow while registering a new listener with shared buffer. | ||
| 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-2023-21643 | Cri | 0.59 | 9.1 | 0.00 | Aug 8, 2023 | Memory corruption due to untrusted pointer dereference in automotive during system call. | ||
| CVE-2024-38420 | Hig | 0.57 | 8.8 | 0.00 | Feb 3, 2025 | Memory corruption while configuring a Hypervisor based input virtual device. | ||
| 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-45555 | Hig | 0.55 | 8.4 | 0.00 | Jan 6, 2025 | Memory corruption can occur if an already verified IFS2 image is overwritten, bypassing boot verification. This allows unauthorized programs to be injected into security-sensitive images, enabling the booting of a tampered IFS2 system image. | ||
| 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-33044 | Hig | 0.55 | 8.4 | 0.00 | Dec 2, 2024 | Memory corruption while Configuring the SMR/S2CR register in Bypass mode. | ||
| CVE-2024-38399 | Hig | 0.55 | 8.4 | 0.00 | Oct 7, 2024 | Memory corruption while processing user packets to generate page faults. | ||
| 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-33045 | Hig | 0.55 | 8.4 | 0.00 | Sep 2, 2024 | Memory corruption when BTFM client sends new messages over Slimbus to ADSP. | ||
| 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.60cvss 9.3epss 0.00
Memory corruption due to buffer copy without checking the size of input in Core while sending SCM command to get write protection information.
- risk 0.60cvss 9.3epss 0.00
Memory corruption due to integer overflow or wraparound in Core while DDR memory assignment.
- risk 0.60cvss 9.3epss 0.00
Memory corruption due to double free in core while initializing the encryption key.
- risk 0.60cvss 9.3epss 0.00
Memory corruption in Core due to time-of-check time-of-use race condition during dump collection in trust zone.
- risk 0.60cvss 9.3epss 0.00
Memory corruption due to buffer copy without checking size of input while running memory sharing tests with large scattered memory.
- risk 0.60cvss 9.3epss 0.00
Memory corruption in Automotive due to integer overflow to buffer overflow while registering a new listener with shared buffer.
- risk 0.59cvss 9.1epss 0.00
Cryptographic issue in GPS HLOS Driver while downloading Qualcomm GNSS assistance data.
- risk 0.59cvss 9.1epss 0.00
Memory corruption due to untrusted pointer dereference in automotive during system call.
- risk 0.57cvss 8.8epss 0.00
Memory corruption while configuring a Hypervisor based input virtual device.
- 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 can occur if an already verified IFS2 image is overwritten, bypassing boot verification. This allows unauthorized programs to be injected into security-sensitive images, enabling the booting of a tampered IFS2 system image.
- 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 while Configuring the SMR/S2CR register in Bypass mode.
- risk 0.55cvss 8.4epss 0.00
Memory corruption while processing user packets to generate page faults.
- 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 when BTFM client sends new messages over Slimbus to ADSP.
- 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 2 of 24