Vulnerabilities > Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')
DATE | CVE | VULNERABILITY TITLE | RISK |
---|---|---|---|
2024-05-01 | CVE-2024-27019 | Race Condition vulnerability in multiple products In the Linux kernel, the following vulnerability has been resolved: netfilter: nf_tables: Fix potential data-race in __nft_obj_type_get() nft_unregister_obj() can concurrent with __nft_obj_type_get(), and there is not any protection when iterate over nf_tables_objects list in __nft_obj_type_get(). | 4.7 |
2024-05-01 | CVE-2024-27020 | Race Condition vulnerability in Linux Kernel In the Linux kernel, the following vulnerability has been resolved: netfilter: nf_tables: Fix potential data-race in __nft_expr_type_get() nft_unregister_expr() can concurrent with __nft_expr_type_get(), and there is not any protection when iterate over nf_tables_expressions list in __nft_expr_type_get(). | 7.0 |
2024-04-17 | CVE-2023-52645 | Race Condition vulnerability in Linux Kernel In the Linux kernel, the following vulnerability has been resolved: pmdomain: mediatek: fix race conditions with genpd If the power domains are registered first with genpd and *after that* the driver attempts to power them on in the probe sequence, then it is possible that a race condition occurs if genpd tries to power them on in the same time. The same is valid for powering them off before unregistering them from genpd. Attempt to fix race conditions by first removing the domains from genpd and *after that* powering down domains. Also first power up the domains and *after that* register them to genpd. | 4.7 |
2024-04-17 | CVE-2024-26910 | Race Condition vulnerability in Linux Kernel In the Linux kernel, the following vulnerability has been resolved: netfilter: ipset: fix performance regression in swap operation The patch "netfilter: ipset: fix race condition between swap/destroy and kernel side add/del/test", commit 28628fa9 fixes a race condition. But the synchronize_rcu() added to the swap function unnecessarily slows it down: it can safely be moved to destroy and use call_rcu() instead. Eric Dumazet pointed out that simply calling the destroy functions as rcu callback does not work: sets with timeout use garbage collectors which need cancelling at destroy which can wait. | 4.7 |
2024-03-28 | CVE-2023-42974 | Race Condition vulnerability in Apple products A race condition was addressed with improved state handling. | 7.0 |
2024-03-11 | CVE-2024-26617 | Race Condition vulnerability in Linux Kernel 6.7/6.7.1/6.7.2 In the Linux kernel, the following vulnerability has been resolved: fs/proc/task_mmu: move mmu notification mechanism inside mm lock Move mmu notification mechanism inside mm lock to prevent race condition in other components which depend on it. | 7.0 |
2024-03-08 | CVE-2024-23235 | Race Condition vulnerability in Apple products A race condition was addressed with additional validation. | 4.7 |
2024-03-08 | CVE-2024-23239 | Race Condition vulnerability in Apple products A race condition was addressed with improved state handling. | 4.7 |
2024-03-08 | CVE-2024-23275 | Race Condition vulnerability in Apple Macos A race condition was addressed with additional validation. | 4.7 |
2024-03-02 | CVE-2023-52517 | Race Condition vulnerability in Linux Kernel In the Linux kernel, the following vulnerability has been resolved: spi: sun6i: fix race between DMA RX transfer completion and RX FIFO drain Previously the transfer complete IRQ immediately drained to RX FIFO to read any data remaining in FIFO to the RX buffer. | 7.0 |