Google

In libexif, there is a possible out of bounds write due to an integer overflow. This could lead to remote escalation of

In the proc filesystem, there is a possible information disclosure due to log information disclosure. This could lead to

In WiFi, there is a possible leak of WiFi state due to a permissions bypass. This could lead to a local information disc

In System Settings, there is a possible permissions bypass due to a cached Linux user ID. This could lead to a local per

In libstagefright, there is a possible use-after-free due to improper locking. This could lead to local escalation of pr

In sensorservice, there is a possible out of bounds write due to a missing bounds check. This could lead to local escala

In Bluetooth, there is a possible out of bounds read due to an incorrect bounds check. This could lead to remote informa

In libxaac there is a possible out of bounds read due to missing bounds check. This could lead to information disclosure

In telephony, there is a possible bypass of user interaction requirements due to missing permission checks. This could l

In MPEG4Extractor, there is a possible out of bounds write due to an integer overflow. This could lead to remote code ex

In libxaac there is a possible out of bounds read due to missing bounds check. This could lead to information disclosure

In Bluetooth, there is a possible out of bounds read due to an incorrect bounds check. This could lead to remote informa

In the Bluetooth stack, there is a possible out of bounds write due to a use after free. This could lead to local escala

In wifilogd, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalation

In Bluetooth, there is a possible out of bounds write due to an integer overflow. This could lead to local escalation of

In libmediaextractor there is a possible out of bounds write due to an integer overflow. This could lead to remote code

In KeyStore, there is a possible storage of symmetric keys in the TEE instead of the strongbox due to a missing strongbo

In libavc there is a possible out of bounds read due to uninitialized data. This could lead to remote information disclo

In NFC, there is a possible out of bounds read due to a missing bounds check. This could lead to local information discl

In Bluetooth, there is a possible out of bounds read due to a missing bounds check. This could lead to remote informatio

In Bluetooth, there is a possible out of bounds read due to a missing bounds check. This could lead to local information

In AAC Codec, there is a missing variable initialization. This could lead to remote information disclosure with no addit

In NFC, there is a possible out of bounds read due to a missing bounds check. This could lead to local information discl

In NFC, there is a possible out of bounds read due to a missing bounds check. This could lead to local information discl

In wpa_supplicant_8, there is a possible out of bounds read due to a missing bounds check. This could lead to local info

In NFC, there is a possible out of bounds read due to a missing bounds check. This could lead to local information discl

In Bluetooth, there is a possible out of bounds read due to a missing bounds check. This could lead to remote informatio

In NFC, there is a possible out of bounds read due to a missing bounds check. This could lead to local information discl

In NFC, there is a possible out of bounds read due to a missing bounds check. This could lead to local information discl

In the NFC stack, there is a possible out of bounds write due to a missing bounds check. This could lead to local escala

In Bluetooth, there is a possible out of bounds read due to a missing bounds check. This could lead to remote informatio

In NFC, there is a possible out of bounds read due to a missing bounds check. This could lead to local information discl

In NFC, there is a possible out of bounds read due to a missing bounds check. This could lead to local information discl

In wpa_supplicant_8, there is a possible out of bounds read due to a missing bounds check. This could lead to remote inf

In wpa_supplicant_8, there is a possible out of bounds read due to an incorrect bounds check. This could lead to remote

In libvpx, there is a possible out of bounds read due to a missing bounds check. This could lead to remote information d

In LG's LAF component, there is a possible leak of information in a protected disk partition due to a missing bounds che

In LG's LAF component, there is a possible leak of information in a protected disk partition due to a missing bounds che

In the Easel driver, there is possible memory corruption due to race conditions. This could lead to local escalation of

In the Easel driver, there is possible memory corruption due to race conditions. This could lead to local escalation of

In libxaac there is a possible information disclosure due to uninitialized data. This could lead to information disclosu

In libxaac there is a possible information disclosure due to uninitialized data. This could lead to information disclosu

In libxaac there is a possible information disclosure due to uninitialized data. This could lead to information disclosu

In libxaac there is a possible information disclosure due to uninitialized data. This could lead to information disclosu

In libxaac there is a possible information disclosure due to uninitialized data. This could lead to information disclosu

In libxaac there is a possible information disclosure due to uninitialized data. This could lead to information disclosu

In libxaac there is a possible information disclosure due to uninitialized data. This could lead to information disclosu

In libxaac there is a possible out of bounds read due to a missing bounds check. This could lead to information disclosu

In libxaac there is a possible out of bounds read due to a missing bounds check. This could lead to information disclosu

In libxaac there is a possible out of bounds read due to a missing bounds check. This could lead to information disclosu