Vulnerabilities > Google > Android > Medium
DATE | CVE | VULNERABILITY TITLE | RISK |
---|---|---|---|
2021-12-15 | CVE-2021-39638 | Use After Free vulnerability in Google Android In periodic_io_work_func of lwis_periodic_io.c, there is a possible out of bounds write due to a use after free. | 6.7 |
2021-12-15 | CVE-2021-39639 | Missing Authorization vulnerability in Google Android In TBD of fvp.c, there is a possible way to glitch CPU behavior due to a missing permission check. | 6.8 |
2021-12-15 | CVE-2021-39642 | Race Condition vulnerability in Google Android In synchronous_process_io_entries of lwis_ioctl.c, there is a possible out of bounds write due to a race condition. | 6.4 |
2021-12-15 | CVE-2021-39643 | Unchecked Return Value vulnerability in Google Android In ic_startRetrieveEntryValue of acropora/app/identity/ic.c, there is a possible bypass of defense-in-depth due to missing validation of the return value. | 6.7 |
2021-12-15 | CVE-2021-39647 | Improper Locking vulnerability in Google Android In mon_smc_load_sp of gs101-sc/plat/samsung/exynos/soc/exynos9845/smc_booting.S, there is a possible reinitialization of TEE due to improper locking. | 4.4 |
2021-12-15 | CVE-2021-39648 | Race Condition vulnerability in Google Android In gadget_dev_desc_UDC_show of configfs.c, there is a possible disclosure of kernel heap memory due to a race condition. | 4.1 |
2021-12-15 | CVE-2021-39649 | Improper Locking vulnerability in Google Android In regmap_exit of regmap.c, there is a possible use-after-free due to improper locking. | 6.7 |
2021-12-15 | CVE-2021-39650 | Out-of-bounds Write vulnerability in Google Android In (TBD) of (TBD), there is a possible out of bounds write due to a missing bounds check. | 6.7 |
2021-12-15 | CVE-2021-39652 | Out-of-bounds Write vulnerability in Google Android In sec_ts_parsing_cmds of (TBD), there is a possible out of bounds write due to an incorrect bounds check. | 6.7 |
2021-12-15 | CVE-2021-39656 | Improper Locking vulnerability in Google Android In __configfs_open_file of file.c, there is a possible use-after-free due to improper locking. | 6.7 |