Show filters
548 Total Results
Displaying 181-190 of 548
Sort by:
Attacker Value
Unknown
CVE-2022-33267
Disclosure Date: June 06, 2023 (last updated February 25, 2025)
Memory corruption in Linux while sending DRM request.
0
Attacker Value
Unknown
CVE-2022-33264
Disclosure Date: June 06, 2023 (last updated February 25, 2025)
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 February 25, 2025)
Memory corruption due to use after free in Core when multiple DCI clients register and deregister.
0
Attacker Value
Unknown
CVE-2022-33230
Disclosure Date: June 06, 2023 (last updated February 25, 2025)
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 February 25, 2025)
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 February 25, 2025)
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 February 25, 2025)
Memory corruption in core due to buffer copy without check9ing the size of input while processing ioctl queries.
0
Attacker Value
Unknown
CVE-2022-22076
Disclosure Date: June 06, 2023 (last updated February 25, 2025)
information disclosure due to cryptographic issue in Core during RPMB read request.
0
Attacker Value
Unknown
CVE-2022-40504
Disclosure Date: May 02, 2023 (last updated February 24, 2025)
Transient DOS due to reachable assertion in Modem when UE received Downlink Data Indication message from the network.
0
Attacker Value
Unknown
CVE-2022-33273
Disclosure Date: May 02, 2023 (last updated February 24, 2025)
Information disclosure due to buffer over-read in Trusted Execution Environment while QRKS report generation.
0
