Vulnerabilities > Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')
| DATE | CVE | VULNERABILITY TITLE | RISK |
|---|---|---|---|
| 2024-07-09 | CVE-2024-31327 | Race Condition vulnerability in Google Android In multiple functions of MessageQueueBase.h, there is a possible out of bounds write due to a race condition. | 7.0 |
| 2024-07-09 | CVE-2024-34724 | Race Condition vulnerability in Google Android In _UnrefAndMaybeDestroy of pmr.c, there is a possible arbitrary code execution due to a race condition. | 7.0 |
| 2024-07-09 | CVE-2024-34725 | Race Condition vulnerability in Google Android In DevmemIntUnexportCtx of devicemem_server.c, there is a possible arbitrary code execution due to a race condition. | 7.0 |
| 2024-07-01 | CVE-2024-6387 | Race Condition vulnerability in multiple products A security regression (CVE-2006-5051) was discovered in OpenSSH's server (sshd). | 8.1 |
| 2024-06-19 | CVE-2021-47599 | Race Condition vulnerability in Linux Kernel In the Linux kernel, the following vulnerability has been resolved: btrfs: use latest_dev in btrfs_show_devname The test case btrfs/238 reports the warning below: WARNING: CPU: 3 PID: 481 at fs/btrfs/super.c:2509 btrfs_show_devname+0x104/0x1e8 [btrfs] CPU: 2 PID: 1 Comm: systemd Tainted: G W O 5.14.0-rc1-custom #72 Hardware name: QEMU QEMU Virtual Machine, BIOS 0.0.0 02/06/2015 Call trace: btrfs_show_devname+0x108/0x1b4 [btrfs] show_mountinfo+0x234/0x2c4 m_show+0x28/0x34 seq_read_iter+0x12c/0x3c4 vfs_read+0x29c/0x2c8 ksys_read+0x80/0xec __arm64_sys_read+0x28/0x34 invoke_syscall+0x50/0xf8 do_el0_svc+0x88/0x138 el0_svc+0x2c/0x8c el0t_64_sync_handler+0x84/0xe4 el0t_64_sync+0x198/0x19c Reason: While btrfs_prepare_sprout() moves the fs_devices::devices into fs_devices::seed_list, the btrfs_show_devname() searches for the devices and found none, leading to the warning as in above. Fix: latest_dev is updated according to the changes to the device list. That means we could use the latest_dev->name to show the device name in /proc/self/mounts, the pointer will be always valid as it's assigned before the device is deleted from the list in remove or replace. The RCU protection is sufficient as the device structure is freed after synchronization. | 4.7 |
| 2024-06-13 | CVE-2024-32891 | Race Condition vulnerability in Google Android In sec_media_unprotect of media.c, there is a possible memory corruption due to a race condition. | 7.0 |
| 2024-06-13 | CVE-2024-32899 | Race Condition vulnerability in Google Android In gpu_pm_power_off_top_nolock of pixel_gpu_power.c, there is a possible compromise of protected memory due to a race condition. | 7.0 |
| 2024-06-13 | CVE-2024-32908 | Race Condition vulnerability in Google Android In sec_media_protect of media.c, there is a possible permission bypass due to a race condition. | 7.8 |
| 2024-06-06 | CVE-2024-2032 | Race Condition vulnerability in Zenml A race condition vulnerability exists in zenml-io/zenml versions up to and including 0.55.3, which allows for the creation of multiple users with the same username when requests are sent in parallel. | 3.1 |
| 2024-06-04 | CVE-2024-28999 | Race Condition vulnerability in Solarwinds Platform The SolarWinds Platform was determined to be affected by a Race Condition Vulnerability affecting the web console. | 8.1 |