Search Results (26 CVEs found)

CVE Vendors Products Updated CVSS v3.1
CVE-2024-45562 1 Qualcomm 160 C-v2x 9150, C-v2x 9150 Firmware, Fastconnect 6800 and 157 more 2025-08-11 6.6 Medium
Memory corruption during concurrent access to server info object due to unprotected critical field.
CVE-2024-45570 1 Qualcomm 116 C-v2x 9150, C-v2x 9150 Firmware, Fastconnect 6800 and 113 more 2025-05-09 6.6 Medium
Memory corruption may occur during IO configuration processing when the IO port count is invalid.
CVE-2024-49838 1 Qualcomm 338 Ar8035, Ar8035 Firmware, Fastconnect 6200 and 335 more 2025-02-05 8.2 High
Information disclosure while parsing the OCI IE with invalid length.
CVE-2023-28577 1 Qualcomm 66 Fastconnect 6800, Fastconnect 6800 Firmware, Fastconnect 6900 and 63 more 2024-11-21 6.7 Medium
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.
CVE-2023-28576 1 Qualcomm 62 Fastconnect 6800, Fastconnect 6800 Firmware, Fastconnect 6900 and 59 more 2024-11-21 6.4 Medium
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.
CVE-2023-28575 1 Qualcomm 120 205, 205 Firmware, 215 and 117 more 2024-11-21 6.7 Medium
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.