Vulnerabilities > Improper Locking
| DATE | CVE | VULNERABILITY TITLE | RISK |
|---|---|---|---|
| 2022-10-07 | CVE-2022-26452 | Improper Locking vulnerability in Google Android In isp, there is a possible use after free due to improper locking. | 6.7 |
| 2022-10-07 | CVE-2022-26473 | Improper Locking vulnerability in Google Android 12.0 In vdec fmt, there is a possible use after free due to improper locking. | 6.7 |
| 2022-09-06 | CVE-2022-26451 | Improper Locking vulnerability in Google Android 12.0 In ged, there is a possible use after free due to improper locking. | 6.7 |
| 2022-08-27 | CVE-2022-38791 | Improper Locking vulnerability in multiple products In MariaDB before 10.9.2, compress_write in extra/mariabackup/ds_compress.cc does not release data_mutex upon a stream write failure, which allows local users to trigger a deadlock. | 5.5 |
| 2022-08-26 | CVE-2021-3735 | Improper Locking vulnerability in multiple products A deadlock issue was found in the AHCI controller device of QEMU. | 4.4 |
| 2022-08-25 | CVE-2022-2959 | Improper Locking vulnerability in Linux Kernel A race condition was found in the Linux kernel's watch queue due to a missing lock in pipe_resize_ring(). | 7.0 |
| 2022-08-24 | CVE-2022-32811 | Improper Locking vulnerability in Apple mac OS X and Macos A memory corruption vulnerability was addressed with improved locking. | 7.8 |
| 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-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-07-06 | CVE-2022-21775 | Improper Locking vulnerability in Google Android 11.0/12.0 In sched driver, there is a possible use after free due to improper locking. | 6.7 |