Show filters
342 Total Results
Displaying 21-30 of 342
Sort by:
Attacker Value
Unknown
CVE-2022-40530
Disclosure Date: March 10, 2023 (last updated October 08, 2023)
Memory corruption in WLAN due to integer overflow to buffer overflow in WLAN during initialization phase.
0
Attacker Value
Unknown
CVE-2022-40515
Disclosure Date: March 10, 2023 (last updated October 08, 2023)
Memory corruption in Video due to double free while playing 3gp clip with invalid metadata atoms.
0
Attacker Value
Unknown
CVE-2022-33278
Disclosure Date: March 10, 2023 (last updated October 08, 2023)
Memory corruption due to buffer copy without checking the size of input in HLOS when input message size is larger than the buffer capacity.
0
Attacker Value
Unknown
CVE-2022-33257
Disclosure Date: March 10, 2023 (last updated October 08, 2023)
Memory corruption in Core due to time-of-check time-of-use race condition during dump collection in trust zone.
0
Attacker Value
Unknown
CVE-2022-33256
Disclosure Date: March 10, 2023 (last updated October 08, 2023)
Memory corruption due to improper validation of array index in Multi-mode call processor.
0
Attacker Value
Unknown
CVE-2022-33254
Disclosure Date: March 10, 2023 (last updated October 08, 2023)
Transient DOS due to reachable assertion in Modem while processing SIB1 Message.
0
Attacker Value
Unknown
CVE-2022-33250
Disclosure Date: March 10, 2023 (last updated October 08, 2023)
Transient DOS due to reachable assertion in modem when network repeatedly sent invalid message container for NR to LTE handover.
0
Attacker Value
Unknown
CVE-2022-33242
Disclosure Date: March 10, 2023 (last updated October 08, 2023)
Memory corruption due to improper authentication in Qualcomm IPC while loading unsigned lib in audio PD.
0
Attacker Value
Unknown
CVE-2022-33213
Disclosure Date: March 10, 2023 (last updated October 08, 2023)
Memory corruption in modem due to buffer overflow while processing a PPP packet
0
Attacker Value
Unknown
CVE-2022-25709
Disclosure Date: March 10, 2023 (last updated October 08, 2023)
Memory corruption in modem due to use of out of range pointer offset while processing qmi msg
0
