Show filters
802 Total Results
Displaying 361-370 of 802
Sort by:
Attacker Value
Unknown
CVE-2022-33287
Disclosure Date: April 13, 2023 (last updated February 24, 2025)
Information disclosure in Modem due to buffer over-read while getting length of Unfragmented headers in an IPv6 packet.
0
Attacker Value
Unknown
CVE-2022-33270
Disclosure Date: April 13, 2023 (last updated February 24, 2025)
Transient DOS due to time-of-check time-of-use race condition in Modem while processing RRC Reconfiguration message.
0
Attacker Value
Unknown
CVE-2022-33269
Disclosure Date: April 13, 2023 (last updated February 24, 2025)
Memory corruption due to integer overflow or wraparound in Core while DDR memory assignment.
0
Attacker Value
Unknown
CVE-2022-33231
Disclosure Date: April 13, 2023 (last updated February 24, 2025)
Memory corruption due to double free in core while initializing the encryption key.
0
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.
0
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.
0
Attacker Value
Unknown
CVE-2022-40535
Disclosure Date: March 10, 2023 (last updated February 24, 2025)
Transient DOS due to buffer over-read in WLAN while sending a packet to device.
0
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.
0
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.
0
Attacker Value
Unknown
CVE-2022-40527
Disclosure Date: March 10, 2023 (last updated February 24, 2025)
Transient DOS due to reachable assertion in WLAN while processing PEER ID populated by TQM.
0
