6 matches found
Astra Linux – Vulnerabilities in Linux 5.10, Linux 5.15
In the Linux kernel, the following vulnerabilities have been resolved: kcm: An annotation was added for the data-race around kcm-rxwait. kcm-rxpsock can be accessed without a read lock in kcmrfree. The read and write operations were also updated accordingly. syzbot reported: BUG: KCSAN: A data-ra...
CVE-2026-68143 net: slip: serialize receive against buffer reallocation
In the Linux kernel, the following vulnerability has been resolved: net: slip: serialize receive against buffer reallocation slreallocbufs replaces rbuff and updates buffsize while holding sl-lock. slipreceivebuf reads those fields and writes through rbuff without holding the lock. An MTU change...
unbounded-spsc: Sender::send pointer-as-value transmute causes OOB read and fake-Arc drop under TX/RX race
Summary Sender::send in src/lib.rs contains an unsafe block in the DISCONNECTED arm that transmutes a raw pointer mut Producer into the bytes of a value-level Consumer. The author's intent, visible in the surrounding comment at lines 386-390, was a value transmute. The shipped code is one level o...
Unity Linux 20.1060e / 20.1070e Security Update: kernel (UTSA-2025-990766)
The Unity Linux 20 host has a package installed that is affected by a vulnerability as referenced in the UTSA-2025-990766 advisory. In the Linux kernel, the following vulnerability has been resolved: kcm: close race conditions on skreceivequeue sk-skreceivequeue is protected by skb queue lock, bu...
CVE-2025-38524
CVE-2025-38524 concerns the Linux kernel, in net/rxrpc/recvmsg.c, where a race between concurrent recvmsg handlers can occur when a call with a queued event is processed by a thread and later requeued by another thread while holding the user_mutex. This can lead to a second thread operating on a ...
CVE-2025-38524 rxrpc: Fix recv-recv race of completed call
In the Linux kernel, the following vulnerability has been resolved: rxrpc: Fix recv-recv race of completed call If a call receives an event such as incoming data, the call gets placed on the socket's queue and a thread in recvmsg can be awakened to go and process it. Once the thread has picked up...