Show filters
607 Total Results
Displaying 171-180 of 607
Sort by:
Attacker Value
Unknown
CVE-2023-21667
Disclosure Date: September 05, 2023 (last updated October 08, 2023)
Transient DOS in Bluetooth HOST while passing descriptor to validate the blacklisted BT keyboard.
0
Attacker Value
Unknown
CVE-2023-21664
Disclosure Date: September 05, 2023 (last updated October 08, 2023)
Memory Corruption in Core Platform while printing the response buffer in log.
0
Attacker Value
Unknown
CVE-2023-21662
Disclosure Date: September 05, 2023 (last updated October 08, 2023)
Memory corruption in Core Platform while printing the response buffer in log.
0
Attacker Value
Unknown
CVE-2023-21654
Disclosure Date: September 05, 2023 (last updated October 08, 2023)
Memory corruption in Audio during playback session with audio effects enabled.
0
Attacker Value
Unknown
CVE-2023-21644
Disclosure Date: September 05, 2023 (last updated October 08, 2023)
Memory corruption in RIL due to Integer Overflow while triggering qcril_uim_request_apdu request.
0
Attacker Value
Unknown
CVE-2023-21636
Disclosure Date: September 05, 2023 (last updated October 08, 2023)
Memory Corruption due to improper validation of array index in Linux while updating adn record.
0
Attacker Value
Unknown
CVE-2022-40524
Disclosure Date: September 05, 2023 (last updated October 08, 2023)
Memory corruption due to buffer over-read in Modem while processing SetNativeHandle RTP service.
0
Attacker Value
Unknown
CVE-2022-33275
Disclosure Date: September 05, 2023 (last updated October 08, 2023)
Memory corruption due to improper validation of array index in WLAN HAL when received lm_itemNum is out of range.
0
Attacker Value
Unknown
CVE-2022-33220
Disclosure Date: September 05, 2023 (last updated October 08, 2023)
Information disclosure in Automotive multimedia due to buffer over-read.
0
Attacker Value
Unknown
CVE-2023-28577
Disclosure Date: August 08, 2023 (last updated October 08, 2023)
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.
0