Show filters
505 Total Results
Displaying 51-60 of 505
Sort by:
Attacker Value
Unknown
CVE-2022-40507
Disclosure Date: June 06, 2023 (last updated October 08, 2023)
Memory corruption due to double free in Core while mapping HLOS address to the list.
0
Attacker Value
Unknown
CVE-2022-33307
Disclosure Date: June 06, 2023 (last updated October 08, 2023)
Memory Corruption due to double free in automotive when a bad HLOS address for one of the lists to be mapped is passed.
0
Attacker Value
Unknown
CVE-2022-33267
Disclosure Date: June 06, 2023 (last updated October 08, 2023)
Memory corruption in Linux while sending DRM request.
0
Attacker Value
Unknown
CVE-2022-33264
Disclosure Date: June 06, 2023 (last updated October 08, 2023)
Memory corruption in modem due to stack based buffer overflow while parsing OTASP Key Generation Request Message.
0
Attacker Value
Unknown
CVE-2022-33263
Disclosure Date: June 06, 2023 (last updated October 08, 2023)
Memory corruption due to use after free in Core when multiple DCI clients register and deregister.
0
Attacker Value
Unknown
CVE-2022-33251
Disclosure Date: June 06, 2023 (last updated October 08, 2023)
Transient DOS due to reachable assertion in Modem because of invalid network configuration.
0
Attacker Value
Unknown
CVE-2022-33230
Disclosure Date: June 06, 2023 (last updated October 08, 2023)
Memory corruption in FM Host due to buffer copy without checking the size of input in FM Host
0
Attacker Value
Unknown
CVE-2022-33227
Disclosure Date: June 06, 2023 (last updated October 08, 2023)
Memory corruption in Linux android due to double free while calling unregister provider after register call.
0
Attacker Value
Unknown
CVE-2022-33226
Disclosure Date: June 06, 2023 (last updated October 08, 2023)
Memory corruption due to buffer copy without checking the size of input in Core while processing ioctl commands from diag client applications.
0
Attacker Value
Unknown
CVE-2022-33224
Disclosure Date: June 06, 2023 (last updated October 08, 2023)
Memory corruption in core due to buffer copy without check9ing the size of input while processing ioctl queries.
0
