Vulnerabilities > Google > Android > High
DATE | CVE | VULNERABILITY TITLE | RISK |
---|---|---|---|
2021-06-21 | CVE-2021-0528 | Double Free vulnerability in Google Android In memory management driver, there is a possible memory corruption due to a double free. | 7.8 |
2021-06-21 | CVE-2021-0529 | Improper Locking vulnerability in Google Android In memory management driver, there is a possible memory corruption due to improper locking. | 7.8 |
2021-06-21 | CVE-2021-0530 | Use of Uninitialized Resource vulnerability in Google Android In memory management driver, there is a possible out of bounds write due to uninitialized data. | 7.8 |
2021-06-21 | CVE-2021-0531 | Use After Free vulnerability in Google Android In memory management driver, there is a possible memory corruption due to a use after free. | 7.8 |
2021-06-21 | CVE-2021-0532 | Race Condition vulnerability in Google Android In memory management driver, there is a possible memory corruption due to a race condition. | 7.0 |
2021-06-21 | CVE-2021-0533 | Race Condition vulnerability in Google Android In memory management driver, there is a possible memory corruption due to a race condition. | 7.0 |
2021-06-11 | CVE-2021-0466 | Use of Insufficiently Random Values vulnerability in Google Android 10.0 In startIpClient of ClientModeImpl.java, there is a possible identifier which could be used to track a device. | 7.5 |
2021-06-11 | CVE-2021-0472 | Incorrect Authorization vulnerability in Google Android 10.0/11.0/9.0 In shouldLockKeyguard of LockTaskController.java, there is a possible way to exit App Pinning without a PIN due to a permissions bypass. | 7.8 |
2021-06-11 | CVE-2021-0473 | Use of Uninitialized Resource vulnerability in Google Android In rw_t3t_process_error of rw_t3t.cc, there is a possible double free due to uninitialized data. | 8.8 |
2021-06-11 | CVE-2021-0475 | Use After Free vulnerability in Google Android 10.0/11.0 In on_l2cap_data_ind of btif_sock_l2cap.cc, there is possible memory corruption due to a use after free. | 8.8 |