Show filters
574 Total Results
Displaying 191-200 of 574
Sort by:
Attacker Value
Unknown

CVE-2022-40539

Disclosure Date: March 10, 2023 (last updated February 24, 2025)
Memory corruption in Automotive Android OS due to improper validation of array index.
Attacker Value
Unknown

CVE-2022-40537

Disclosure Date: March 10, 2023 (last updated February 24, 2025)
Memory corruption in Bluetooth HOST while processing the AVRC_PDU_GET_PLAYER_APP_VALUE_TEXT AVRCP response.
Attacker Value
Unknown

CVE-2022-40531

Disclosure Date: March 10, 2023 (last updated February 24, 2025)
Memory corruption in WLAN due to incorrect type cast while sending WMI_SCAN_SCH_PRIO_TBL_CMDID message.
Attacker Value
Unknown

CVE-2022-40530

Disclosure Date: March 10, 2023 (last updated February 24, 2025)
Memory corruption in WLAN due to integer overflow to buffer overflow in WLAN during initialization phase.
Attacker Value
Unknown

CVE-2022-40515

Disclosure Date: March 10, 2023 (last updated February 24, 2025)
Memory corruption in Video due to double free while playing 3gp clip with invalid metadata atoms.
Attacker Value
Unknown

CVE-2022-33260

Disclosure Date: March 10, 2023 (last updated February 24, 2025)
Memory corruption due to stack based buffer overflow in core while sending command from USB of large size.
Attacker Value
Unknown

CVE-2022-33245

Disclosure Date: March 10, 2023 (last updated February 24, 2025)
Memory corruption in WLAN due to use after free
Attacker Value
Unknown

CVE-2022-33242

Disclosure Date: March 10, 2023 (last updated February 24, 2025)
Memory corruption due to improper authentication in Qualcomm IPC while loading unsigned lib in audio PD.
Attacker Value
Unknown

CVE-2022-33213

Disclosure Date: March 10, 2023 (last updated February 24, 2025)
Memory corruption in modem due to buffer overflow while processing a PPP packet
Attacker Value
Unknown

CVE-2022-25705

Disclosure Date: March 10, 2023 (last updated February 24, 2025)
Memory corruption in modem due to integer overflow to buffer overflow while handling APDU response