Show filters
837 Total Results
Displaying 191-200 of 837
Sort by:
Attacker Value
Unknown
CVE-2023-28544
Disclosure Date: September 05, 2023 (last updated February 25, 2025)
Memory corruption in WLAN while sending transmit command from HLOS to UTF handlers.
0
Attacker Value
Unknown
CVE-2023-28538
Disclosure Date: September 05, 2023 (last updated February 25, 2025)
Memory corruption in WIN Product while invoking WinAcpi update driver in the UEFI region.
0
Attacker Value
Unknown
CVE-2023-21664
Disclosure Date: September 05, 2023 (last updated February 25, 2025)
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 February 25, 2025)
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 February 25, 2025)
Memory corruption in Audio during playback session with audio effects enabled.
0
Attacker Value
Unknown
CVE-2023-21646
Disclosure Date: September 05, 2023 (last updated February 25, 2025)
Transient DOS in Modem while processing invalid System Information Block 1.
0
Attacker Value
Unknown
CVE-2023-21644
Disclosure Date: September 05, 2023 (last updated February 25, 2025)
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 February 25, 2025)
Memory Corruption due to improper validation of array index in Linux while updating adn record.
0
Attacker Value
Unknown
CVE-2022-33275
Disclosure Date: September 05, 2023 (last updated February 25, 2025)
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-2023-28575
Disclosure Date: August 08, 2023 (last updated February 25, 2025)
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.
0
