Vulnerabilities > Google > Android > High
| DATE | CVE | VULNERABILITY TITLE | RISK |
|---|---|---|---|
| 2022-01-14 | CVE-2021-39627 | Incorrect Permission Assignment for Critical Resource vulnerability in Google Android In sendLegacyVoicemailNotification of LegacyModeSmsHandler.java, there is a possible permissions bypass due to an unsafe PendingIntent. | 7.8 |
| 2022-01-14 | CVE-2021-39629 | Use After Free vulnerability in Google Android In phTmlNfc_Init and phTmlNfc_CleanUp of phTmlNfc.cc, there is a possible use after free due to a race condition. | 7.0 |
| 2022-01-14 | CVE-2021-39630 | Incorrect Authorization vulnerability in Google Android 12.0 In executeRequest of OverlayManagerService.java, there is a possible way to control fabricated overlays from adb shell due to a permissions bypass. | 7.8 |
| 2022-01-14 | CVE-2021-39632 | Out-of-bounds Write vulnerability in Google Android 11.0/12.0 In inotify_cb of events.cpp, there is a possible out of bounds write due to an incorrect bounds check. | 7.8 |
| 2022-01-14 | CVE-2021-39634 | Use After Free vulnerability in Google Android In fs/eventpoll.c, there is a possible use after free. | 7.8 |
| 2022-01-14 | CVE-2021-39678 | Unspecified vulnerability in Google Android In <TBD> of <TBD>, there is a possible bypass of Factory Reset Protection due to <TBD>. | 7.8 |
| 2022-01-14 | CVE-2021-39679 | Use After Free vulnerability in Google Android In init of vendor_graphicbuffer_meta.cpp, there is a possible use after free due to a race condition. | 7.0 |
| 2022-01-14 | CVE-2021-39681 | Use After Free vulnerability in Google Android In delete_protocol of main.c, there is a possible arbitrary code execution due to a use after free. | 7.8 |
| 2022-01-14 | CVE-2021-39682 | Out-of-bounds Write vulnerability in Google Android In mgm_alloc_page of memory_group_manager.c, there is a possible out of bounds write due to an incorrect bounds check. | 7.8 |
| 2022-01-14 | CVE-2021-39684 | Unspecified vulnerability in Google Android 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. | 7.8 |