CPE Details
Qualcomm Snapdragon X55 5G Firmware -
-
2023-07-10
08h49 +00:00
08h49 +00:00
2023-09-02
00h30 +00:00
00h30 +00:00
Alerte pour un CPE
Stay informed of any changes for a specific CPE.
CPE Name: cpe:2.3:o:qualcomm:snapdragon_x55_5g_firmware:-:*:*:*:*:*:*:*
Informations
Vendor
qualcommProduct
snapdragon_x55_5g_firmwareVersion
-Related CVE
| CVE ID | Published | Description | Score | Severity |
|---|---|---|---|---|
| Information disclosure while deriving keys for a session for any Widevine use case. | 5.5 |
Medium |
||
| Memory corruption in Graphics while processing user packets for command submission. | 8.4 |
High |
||
| Transient DOS in WLAN Firmware while interpreting MBSSID IE of a received beacon frame. | 7.5 |
High |
||
| Memory corruption in WLAN HAL while parsing WMI command parameters. | 7.8 |
High |
||
| Memory corruption in WLAN HAL while handling command through WMI interfaces. | 7.8 |
High |
||
| Memory corruption in WLAN HAL while handling command streams through WMI interfaces. | 7.8 |
High |
||
| Memory corruption while handling payloads from remote ESL. | 9.8 |
Critical |
||
| In the function call related to CAM_REQ_MGR_RELEASE_BUF there is no check if the buffer is being used. So when a function called cam_mem_get_cpu_buf to get the kernel va to use, another thread can call CAM_REQ_MGR_RELEASE_BUF to unmap the kernel va which cause UAF of the kernel address. | 7.8 |
High |
||
| The buffer obtained from kernel APIs such as cam_mem_get_cpu_buf() may be readable/writable in userspace after kernel accesses it. In other words, user mode may race and modify the packet header (e.g. header.count), causing checks (e.g. size checks) in kernel code to be invalid. This may lead to out-of-bounds read/write issues. | 7 |
High |
||
| The cam_get_device_priv function does not check the type of handle being returned (device/session/link). This would lead to invalid type usage if a wrong handle is passed to it. | 7.8 |
High |
||
| Memory Corruption in WLAN HOST while fetching TX status information. | 7.8 |
High |
||
| Memory Corruption in Data Modem while processing DMA buffer release event about CFR data. | 7.8 |
High |
||
| Memory Corruption in WLAN HOST while parsing QMI WLAN Firmware response message. | 7.8 |
High |
||
| Memory Corruption in WLAN HOST while parsing QMI response message from firmware. | 7.8 |
High |
||
| Memory Corruption in Audio while allocating the ion buffer during the music playback. | 8.4 |
High |
||
| Arbitrary memory overwrite when VM gets compromised in TX write leading to Memory Corruption. | 7.8 |
High |
||
| Memory Corruption in WLAN HOST while processing WLAN FW request to allocate memory. | 7.8 |
High |
||
| Memory corruption in Video while calling APIs with different instance ID than the one received in initialization. | 7.8 |
High |
||
| Memory corruption in Linux while calling system configuration APIs. | 7.8 |
High |
||
| Memory Corruption in Data Network Stack & Connectivity when sim gets detected on telephony. | 7.8 |
High |
||
| Memory Corruption in Linux while processing QcRilRequestImsRegisterMultiIdentityMessage request. | 7.8 |
High |
||
| Weak Configuration due to improper input validation in Modem while processing LTE security mode command message received from network. | 9.8 |
Critical |
||
| Memory Corruption in Modem due to double free while parsing the PKCS15 sim files. | 6.8 |
Medium |
||
| Information disclosure in DSP Services while loading dynamic module. | 6.2 |
Medium |
2025©
tesweb SA
