Vulnerabilities > Google > Android > Medium
| DATE | CVE | VULNERABILITY TITLE | RISK |
|---|---|---|---|
| 2022-08-11 | CVE-2022-20369 | Out-of-bounds Write vulnerability in multiple products In v4l2_m2m_querybuf of v4l2-mem2mem.c, there is a possible out of bounds write due to improper input validation. | 6.7 |
| 2022-08-11 | CVE-2022-20371 | Improper Locking vulnerability in Google Android In dm_bow_dtr and related functions of dm-bow.c, there is a possible use after free due to a race condition. | 6.4 |
| 2022-08-11 | CVE-2022-20372 | Use After Free vulnerability in Google Android In exynos5_i2c_irq of (TBD), there is a possible out of bounds write due to a use after free. | 6.7 |
| 2022-08-11 | CVE-2022-20373 | Race Condition vulnerability in Google Android In st21nfc_loc_set_polaritymode of fc/st21nfc.c, there is a possible use after free due to a race condition. | 6.4 |
| 2022-08-11 | CVE-2022-20376 | Improper Locking vulnerability in Google Android In trusty_log_seq_start of trusty-log.c, there is a possible use after free due to improper locking. | 6.7 |
| 2022-08-11 | CVE-2022-20377 | Unspecified vulnerability in Google Android In TBD of keymaster_ipc.cpp, there is a possible to force gatekeeper, fingerprint, and faceauth to use a known HMAC key. | 6.7 |
| 2022-08-11 | CVE-2022-20379 | Use After Free vulnerability in Google Android In lwis_buffer_alloc of lwis_buffer.c, there is a possible arbitrary code execution due to a use after free. | 6.7 |
| 2022-08-11 | CVE-2022-20382 | Uncontrolled Recursion vulnerability in Google Android In (TBD) of (TBD), there is a possible out of bounds write due to kernel stack overflow. | 6.7 |
| 2022-08-10 | CVE-2022-20346 | Out-of-bounds Read vulnerability in Google Android In updateAudioTrackInfoFromESDS_MPEG4Audio of MPEG4Extractor.cpp, there is a possible out of bounds read due to an incorrect bounds check. | 6.5 |
| 2022-08-10 | CVE-2022-20350 | Improper Input Validation vulnerability in Google Android In onCreate of NotificationAccessConfirmationActivity.java, there is a possible way to trick the victim to grant notification access to the wrong app due to improper input validation. | 5.5 |