Sa8540p Firmware
by Qualcomm
CVEs (238)
| CVE | Vendor / Product | Sev | Risk | CVSS | EPSS | KEV | Published | Description |
|---|---|---|---|---|---|---|---|---|
| CVE-2024-45569 | Cri | 0.64 | 9.8 | 0.00 | Feb 3, 2025 | Memory corruption while parsing the ML IE due to invalid frame content. | ||
| 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-2023-43538 | Cri | 0.60 | 9.3 | 0.00 | Jun 3, 2024 | Memory corruption in TZ Secure OS while Tunnel Invoke Manager initialization. | ||
| 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-21651 | Cri | 0.60 | 9.3 | 0.00 | Aug 8, 2023 | Memory Corruption in Core due to incorrect type conversion or cast in secure_io_read/write function in TEE. | ||
| 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-2021-35122 | Cri | 0.60 | 9.3 | 0.00 | Sep 2, 2022 | Non-secure region can try modifying RG permissions of IO space xPUs due to improper input validation in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Wearables | ||
| CVE-2021-35090 | Cri | 0.60 | 9.3 | 0.00 | Jun 14, 2022 | Possible hypervisor memory corruption due to TOC TOU race condition when updating address mappings in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Industrial IOT, Snapdragon Mobile | ||
| 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. |
- risk 0.64cvss 9.8epss 0.00
Memory corruption while parsing the ML IE due to invalid frame content.
- risk 0.60cvss 9.3epss 0.00
Memory corruption in Hypervisor when platform information mentioned is not aligned.
- risk 0.60cvss 9.3epss 0.00
Memory corruption in TZ Secure OS while Tunnel Invoke Manager initialization.
- 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.60cvss 9.3epss 0.00
Memory Corruption in Core due to incorrect type conversion or cast in secure_io_read/write function in TEE.
- 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.60cvss 9.3epss 0.00
Non-secure region can try modifying RG permissions of IO space xPUs due to improper input validation in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Wearables
- risk 0.60cvss 9.3epss 0.00
Possible hypervisor memory corruption due to TOC TOU race condition when updating address mappings in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Industrial IOT, Snapdragon Mobile
- 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.
Page 1 of 12