← Back

Android

android

Vendor: Google • 8,153 CVEs

CVEs (8,153)

CVE
VENDORS
PRODUCTS
UPDATED
PUBLISHED
CVSS
1Google
1Android
Jun 17, 2026
Feb 9, 2022
N/A· v4
4.4 MEDIUM· v3
2.1 LOW· v2
In vcu driver, there is a possible information disclosure due to a use after free. This could lead to local escalation of privilege with System execution privileges needed. User interaction is not needed for exploitation...Show more
In vcu driver, there is a possible information disclosure due to a use after free. This could lead to local escalation of privilege with System execution privileges needed. User interaction is not needed for exploitation. Patch ID: ALPS06171675; Issue ID: ALPS06171675.Show less
1Google
1Android
Jun 17, 2026
Feb 9, 2022
N/A· v4
6.8 MEDIUM· v3
4.6 MEDIUM· v2
In Preloader XFLASH, there is a possible escalation of privilege due to an improper certificate validation. This could lead to local escalation of privilege for an attacker who has physical access to the device with no a...Show more
In Preloader XFLASH, there is a possible escalation of privilege due to an improper certificate validation. This could lead to local escalation of privilege for an attacker who has physical access to the device with no additional execution privileges needed. User interaction is not needed for exploitation. Patch ID: ALPS06160806; Issue ID: ALPS06160806.Show less
1Google
1Android
Jun 17, 2026
Feb 9, 2022
N/A· v4
4.4 MEDIUM· v3
2.1 LOW· v2
In camera driver, there is a possible out of bounds read due to an incorrect bounds check. This could lead to local information disclosure with System execution privileges needed. User interaction is not needed for explo...Show more
In camera driver, there is a possible out of bounds read due to an incorrect bounds check. This could lead to local information disclosure with System execution privileges needed. User interaction is not needed for exploitation. Patch ID: ALPS05862973; Issue ID: ALPS05862973.Show less
1Google
1Android
Jun 17, 2026
Feb 9, 2022
N/A· v4
4.1 MEDIUM· v3
1.9 LOW· v2
In vow driver, there is a possible memory corruption due to a race condition. This could lead to local information disclosure with System execution privileges needed. User interaction is not needed for exploitation. Patc...Show more
In vow driver, there is a possible memory corruption due to a race condition. This could lead to local information disclosure with System execution privileges needed. User interaction is not needed for exploitation. Patch ID: ALPS05852822; Issue ID: ALPS05852822.Show less
1Google
1Android
Jun 17, 2026
Feb 9, 2022
N/A· v4
7.8 HIGH· v3
4.6 MEDIUM· v2
In fb driver, there is a possible memory corruption due to a use after free. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitatio...Show more
In fb driver, there is a possible memory corruption due to a use after free. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation. Patch ID: ALPS05850708; Issue ID: ALPS05850708.Show less
1Google
1Android
Jun 17, 2026
Feb 9, 2022
N/A· v4
6.7 MEDIUM· v3
4.6 MEDIUM· v2
In vow driver, there is a possible out of bounds write due to a stack-based buffer overflow. This could lead to local escalation of privilege with System execution privileges needed. User interaction is not needed for ex...Show more
In vow driver, there is a possible out of bounds write due to a stack-based buffer overflow. This could lead to local escalation of privilege with System execution privileges needed. User interaction is not needed for exploitation. Patch ID: ALPS05837793; Issue ID: ALPS05837793.Show less
1Google
1Android
Jun 17, 2026
Feb 9, 2022
N/A· v4
4.4 MEDIUM· v3
2.1 LOW· v2
In cmdq driver, there is a possible out of bounds read due to an incorrect bounds check. This could lead to local information disclosure with System execution privileges needed. User interaction is not needed for exploit...Show more
In cmdq driver, there is a possible out of bounds read due to an incorrect bounds check. This could lead to local information disclosure with System execution privileges needed. User interaction is not needed for exploitation. Patch ID: ALPS05747150; Issue ID: ALPS05747150.Show less
1Google
1Android
Jun 17, 2026
Feb 9, 2022
N/A· v4
7.8 HIGH· v3
4.6 MEDIUM· v2
In Bluetooth, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exp...Show more
In Bluetooth, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation. Patch ID: ALPS06198663; Issue ID: ALPS06198663.Show less
1Google
1Android
Jun 17, 2026
Feb 9, 2022
N/A· v4
7.8 HIGH· v3
4.6 MEDIUM· v2
In Bluetooth, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exp...Show more
In Bluetooth, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation. Patch ID: ALPS06126826; Issue ID: ALPS06126826.Show less
1Google
1Android
Jun 17, 2026
Feb 9, 2022
N/A· v4
7.8 HIGH· v3
4.6 MEDIUM· v2
In Bluetooth, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exp...Show more
In Bluetooth, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation. Patch ID: ALPS06126827; Issue ID: ALPS06126827.Show less
1Google
1Android
Jun 17, 2026
Feb 9, 2022
N/A· v4
7.8 HIGH· v3
4.6 MEDIUM· v2
In Bluetooth, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exp...Show more
In Bluetooth, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation. Patch ID: ALPS06126832; Issue ID: ALPS06126832.Show less
1Google
1Android
Jun 17, 2026
Feb 9, 2022
N/A· v4
7.8 HIGH· v3
4.6 MEDIUM· v2
In system service, there is a possible permission bypass due to a missing permission check. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed...Show more
In system service, there is a possible permission bypass due to a missing permission check. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation. Patch ID: ALPS06219064; Issue ID: ALPS06219064.Show less
1Google
1Android
Jun 17, 2026
Feb 9, 2022
N/A· v4
5.5 MEDIUM· v3
2.1 LOW· v2
In ion driver, there is a possible information disclosure due to an incorrect bounds check. This could lead to local information disclosure with no additional execution privileges needed. User interaction is not needed f...Show more
In ion driver, there is a possible information disclosure due to an incorrect bounds check. This could lead to local information disclosure with no additional execution privileges needed. User interaction is not needed for exploitation. Patch ID: ALPS05862991; Issue ID: ALPS05862991.Show less
1Google
1Android
Jun 17, 2026
Jan 21, 2022
N/A· v4
6.1 MEDIUM· v3
6.6 MEDIUM· v2
Attacker can reset the device with AT Command in the process of rebooting the device. The LG ID is LVE-SMP-210011.
1Google
1Android
Jun 17, 2026
Jan 14, 2022
N/A· v4
7.8 HIGH· v3
7.2 HIGH· v2
In target_init of gs101/abl/target/slider/target.c, there is a possible allocation of RWX memory due to a logic error in the code. This could lead to local escalation of privilege with no additional execution privileges...Show more
In target_init of gs101/abl/target/slider/target.c, there is a possible allocation of RWX memory due to a logic error in the code. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.Product: AndroidVersions: Android kernelAndroid ID: A-203250788References: N/AShow less
1Google
1Android
Jun 17, 2026
Jan 14, 2022
N/A· v4
6.7 MEDIUM· v3
7.2 HIGH· v2
In copy_from_mbox of sss_ice_util.c, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalation of privilege with System execution privileges needed. User interaction is no...Show more
In copy_from_mbox of sss_ice_util.c, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalation of privilege with System execution privileges needed. User interaction is not needed for exploitation.Product: AndroidVersions: Android kernelAndroid ID: A-202003354References: N/AShow less
1Google
1Android
Jun 17, 2026
Jan 14, 2022
N/A· v4
7.8 HIGH· v3
7.2 HIGH· v2
In mgm_alloc_page of memory_group_manager.c, there is a possible out of bounds write due to an incorrect bounds check. This could lead to local escalation of privilege with no additional execution privileges needed. User...Show more
In mgm_alloc_page of memory_group_manager.c, there is a possible out of bounds write due to an incorrect bounds check. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.Product: AndroidVersions: Android kernelAndroid ID: A-201677538References: N/AShow less
1Google
1Android
Jun 17, 2026
Jan 14, 2022
N/A· v4
7.8 HIGH· v3
4.6 MEDIUM· v2
In delete_protocol of main.c, there is a possible arbitrary code execution due to a use after free. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not...Show more
In delete_protocol of main.c, there is a possible arbitrary code execution due to a use after free. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.Product: AndroidVersions: Android kernelAndroid ID: A-200251074References: N/AShow less
1Google
1Android
Jun 17, 2026
Jan 14, 2022
N/A· v4
4.4 MEDIUM· v3
2.1 LOW· v2
In sec_SHA256_Transform of sha256_core.c, there is a possible way to read heap data due to uninitialized data. This could lead to local information disclosure with System execution privileges needed. User interaction is...Show more
In sec_SHA256_Transform of sha256_core.c, there is a possible way to read heap data due to uninitialized data. This could lead to local information disclosure with System execution privileges needed. User interaction is not needed for exploitation.Product: AndroidVersions: Android kernelAndroid ID: A-197965864References: N/AShow less
1Google
1Android
Jun 17, 2026
Jan 14, 2022
N/A· v4
7.0 HIGH· v3
6.9 MEDIUM· v2
In init of vendor_graphicbuffer_meta.cpp, there is a possible use after free due to a race condition. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is n...Show more
In init of vendor_graphicbuffer_meta.cpp, there is a possible use after free due to a race condition. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.Product: AndroidVersions: Android kernelAndroid ID: A-188745089References: N/AShow less