11 matches found
CVE-2026-58098
When semop2 blocks waiting for a semaphore condition, it releases the per-set lock and sleeps. Upon waking, it checks the sequence number embedded in the semaphore set's IPC identifier to detect whether the set was removed while the caller was asleep. This sequence number is only 15 bits wide. If...
EUVD-2026-101855
When semop2 blocks waiting for a semaphore condition, it releases the per-set lock and sleeps. Upon waking, it checks the sequence number embedded in the semaphore set's IPC identifier to detect whether the set was removed while the caller was asleep. This sequence number is only 15 bits wide. If...
CVE-2026-58098
When semop2 blocks waiting for a semaphore condition, it releases the per-set lock and sleeps. Upon waking, it checks the sequence number embedded in the semaphore set's IPC identifier to detect whether the set was removed while the caller was asleep. This sequence number is only 15 bits wide. If...
CVE-2026-58098
The FreeBSD kernel is vulnerable to a heap out-of-bounds access in the semop(2) system call. The issue arises because the 15-bit sequence number used to verify if a semaphore set was removed while a process was sleeping can wrap around if many sets are created and destroyed quickly. This allows a...
CVE-2026-58098 Heap out-of-bounds access in semop(2)
When semop2 blocks waiting for a semaphore condition, it releases the per-set lock and sleeps. Upon waking, it checks the sequence number embedded in the semaphore set's IPC identifier to detect whether the set was removed while the caller was asleep. This sequence number is only 15 bits wide. If...
CVE-2026-58098 Heap out-of-bounds access in semop(2)
When semop2 blocks waiting for a semaphore condition, it releases the per-set lock and sleeps. Upon waking, it checks the sequence number embedded in the semaphore set's IPC identifier to detect whether the set was removed while the caller was asleep. This sequence number is only 15 bits wide. If...
CVE-2026-58098: Out-of-bounds Write
When semop2 blocks waiting for a semaphore condition, it releases the per-set lock and sleeps. Upon waking, it checks the sequence number embedded in the semaphore set's IPC identifier to detect whether the set was removed while the caller was asleep. This sequence number is only 15 bits wide. If...
FreeBSD : FreeBSD -- Heap out-of-bounds access in semop(2) (6ef25129-bccc-11f1-906f-bc241121aa0a)
The version of FreeBSD installed on the remote host is prior to tested version. It is, therefore, affected by a vulnerability as referenced in the 6ef25129-bccc-11f1-906f-bc241121aa0a advisory. When semop2 blocks waiting for a semaphore condition, it releases the per-set lock and sleeps. Upon...
FreeBSD Security Advisory - FreeBSD-SA-26:64.sysvsem
FreeBSD Security Advisory - Heap out-of-bounds access in semop2. An unprivileged local user can trigger an out-of-bounds access on kernel heap memory, potentially leading to privilege escalation...
FreeBSD-SA-26:64.sysvsem
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 ============================================================================= FreeBSD-SA-26:64.sysvsem Security Advisory The FreeBSD Project Topic: Heap out-of-bounds access in semop2 Category: core Module: sysvsem Announced: 2026-09-29 Credits: Reo...
FreeBSD -- Heap out-of-bounds access in semop(2)
Problem Description: When semop2 blocks waiting for a semaphore condition, it releases the per-set lock and sleeps. Upon waking, it checks the sequence number embedded in the semaphore set's IPC identifier to detect whether the set was removed while the caller was asleep. This sequence number is...