60 matches found
CVE-2025-54602
An issue was discovered in the Wi-Fi driver in Samsung Mobile Processor and Wearable Processor Exynos 980, 850, 1080, 1280, 1330, 1380, 1480, 1580, W920, W930, and W1000. Improper synchronization on a global variable leads to a use-after-free. An attacker can trigger a race condition by invoking ...
CVE-2025-54601
CVE-2025-54601 affects Samsung Wi‑Fi drivers for Mobile Processor and Wearable Processor Exynos 980, 850, 1080, 1280, 1330, 1380, 1480, 1580, and W9xx/W1000; the root cause is improper synchronization on a global variable that enables a race condition and a double free when an ioctl is invoked co...
Samsung多款产品 安全漏洞
SAMSUNG Mobile Processor and SAMSUNG Wearable Processor are both products of South Korean company Samsung. The SAMSUNG Mobile Processor is a series of mobile processors, while the SAMSUNG Wearable Processor is a series of wearable processors. Several Samsung products have security vulnerabilities...
PT-2026-5671
Memory Corruption when multiple threads simultaneously access a memory free API...
CVE-2025-47356
Memory Corruption when multiple threads concurrently access and modify shared resources...
EUVD-2019-11932
Malware in sbrugna...
EUVD-2017-6358
Malware in sbrugna...
EUVD-2017-9327
Malware in sbrugna...
EUVD-2024-30798
Malicious code in bioql PyPI...
CVE-2025-47316 Double Free in Video
Memory corruption due to double free when multiple threads race to set the timestamp store...
PT-2025-39279
Name of the Vulnerable Software and Affected Versions Affected versions not specified Description A memory corruption issue exists due to a double free condition when multiple threads simultaneously attempt to set the timestamp store. This can lead to instability or potential code execution...
PT-2025-32121 · Microsoft · Windows
Name of the Vulnerable Software and Affected Versions: affected versions not specified Description: A memory corruption issue exists when processing an IOCTL command with concurrent mapping and unmapping of buffers by multiple threads. Recommendations: At the moment, there is no information about...
PT-2025-33567
Name of the Vulnerable Software and Affected Versions: Linux kernel affected versions not specified Description: A race condition exists in the rxrpc subsystem where a call can be processed by multiple threads concurrently. This occurs when a call is placed on the socket queue and multiple thread...
CVE-2024-33053
Memory corruption when multiple threads try to unregister the CVP buffer at the same time...
CVE-2019-19396
illumos, as used in OmniOS Community Edition before r151030y, allows a kernel crash via an application with multiple threads calling sendmsg concurrently over a single socket, because uts/common/inet/ip/ipattr.c mishandles connixa dereferences...
CVE-2025-21436
Memory corruption may occur while initiating two IOCTL calls simultaneously to create processes from two different threads...
Azure Linux 3.0 Security Update: kernel (CVE-2024-56670)
The version of kernel installed on the remote Azure Linux 3.0 host is prior to tested version. It is, therefore, affected by a vulnerability as referenced in the CVE-2024-56670 advisory. - In the Linux kernel, the following vulnerability has been resolved: usb: gadget: userial: Fix the issue that...
UBUNTU-CVE-2025-21749
In the Linux kernel, the following vulnerability has been resolved: net: rose: lock the socket in rosebind syzbot reported a soft lockup in roseloopbacktimer, with a repro calling bind from multiple threads. rosebind must lock the socket to avoid this issue...
CVE-2025-21749
In the Linux kernel, the following vulnerability has been resolved: net: rose: lock the socket in rosebind syzbot reported a soft lockup in roseloopbacktimer, with a repro calling bind from multiple threads. rosebind must lock the socket to avoid this issue...
UBUNTU-CVE-2022-49647
In the Linux kernel, the following vulnerability has been resolved: cgroup: Use separate src/dst nodes when preloading csssets for migration Each cset cssset is pinned by its tasks. When we're moving tasks around across csets for a migration, we need to hold the source and destination csets to...