Show filters
222 Total Results
Displaying 31-40 of 222
Sort by:
Attacker Value
Unknown

CVE-2024-33032

Disclosure Date: November 04, 2024 (last updated November 08, 2024)
Memory corruption when the user application modifies the same shared memory asynchronously when kernel is accessing it.
Attacker Value
Unknown

CVE-2024-33030

Disclosure Date: November 04, 2024 (last updated November 08, 2024)
Memory corruption while parsing IPC frequency table parameters for LPLH that has size greater than expected size.
Attacker Value
Unknown

CVE-2024-23385

Disclosure Date: November 04, 2024 (last updated November 08, 2024)
Transient DOS as modem reset occurs when an unexpected MAC RAR (with invalid PDU length) is seen at UE.
Attacker Value
Unknown

CVE-2024-23377

Disclosure Date: November 04, 2024 (last updated November 08, 2024)
Memory corruption while invoking IOCTL command from user-space, when a user modifies the original packet size of the command after system properties have been already sent to the EVA driver.
Attacker Value
Unknown

CVE-2024-43047

Disclosure Date: October 07, 2024 (last updated October 10, 2024)
Memory corruption while maintaining memory maps of HLOS memory.
Attacker Value
Unknown

CVE-2024-38425

Disclosure Date: October 07, 2024 (last updated October 17, 2024)
Information disclosure while sending implicit broadcast containing APP launch information.
Attacker Value
Unknown

CVE-2024-38397

Disclosure Date: October 07, 2024 (last updated October 17, 2024)
Transient DOS while parsing probe response and assoc response frame.
Attacker Value
Unknown

CVE-2024-33073

Disclosure Date: October 07, 2024 (last updated October 17, 2024)
Information disclosure while parsing the BSS parameter change count or MLD capabilities fields of the ML IE.
Attacker Value
Unknown

CVE-2024-23379

Disclosure Date: October 07, 2024 (last updated October 17, 2024)
Memory corruption while unmapping the fastrpc map when two threads can free the same map in concurrent scenario.
Attacker Value
Unknown

CVE-2024-23374

Disclosure Date: October 07, 2024 (last updated October 17, 2024)
Memory corruption is possible when an attempt is made from userspace or console to write some haptics effects pattern to the haptics debugfs file.