Vulnerabilities > Improper Locking
| DATE | CVE | VULNERABILITY TITLE | RISK |
|---|---|---|---|
| 2022-06-15 | CVE-2022-20141 | Improper Locking vulnerability in Google Android In ip_check_mc_rcu of igmp.c, there is a possible use after free due to improper locking. | 7.0 |
| 2022-06-15 | CVE-2022-20153 | Improper Locking vulnerability in Google Android In rcu_cblist_dequeue of rcu_segcblist.c, there is a possible use-after-free due to improper locking. | 6.7 |
| 2022-05-25 | CVE-2022-31621 | Improper Locking vulnerability in Mariadb MariaDB Server before 10.7 is vulnerable to Denial of Service. | 5.5 |
| 2022-05-25 | CVE-2022-31622 | Improper Locking vulnerability in Mariadb MariaDB Server before 10.7 is vulnerable to Denial of Service. | 5.5 |
| 2022-05-25 | CVE-2022-31623 | Improper Locking vulnerability in Mariadb MariaDB Server before 10.7 is vulnerable to Denial of Service. | 5.5 |
| 2022-05-25 | CVE-2022-31624 | Improper Locking vulnerability in Mariadb MariaDB Server before 10.7 is vulnerable to Denial of Service. | 5.5 |
| 2022-04-12 | CVE-2021-39801 | Improper Locking vulnerability in Google Android In ion_ioctl of ion-ioctl.c, there is a possible use after free due to improper locking. | 7.8 |
| 2022-04-07 | CVE-2021-43429 | Improper Locking vulnerability in Seagate Cortx-S3 Server 20211107 A Denial of Service vulnerability exists in CORTX-S3 Server as of 11/7/2021 via the mempool_destroy method due to a failture to release locks pool->lock. | 7.5 |
| 2022-04-05 | CVE-2022-26356 | Improper Locking vulnerability in multiple products Racy interactions between dirty vram tracking and paging log dirty hypercalls Activation of log dirty mode done by XEN_DMOP_track_dirty_vram (was named HVMOP_track_dirty_vram before Xen 4.9) is racy with ongoing log dirty hypercalls. | 5.6 |
| 2022-03-25 | CVE-2021-4147 | Improper Locking vulnerability in multiple products A flaw was found in the libvirt libxl driver. | 6.5 |