CVE-2026-58087

published 19 Aug 2026 · updated 20 Aug 2026

Heap out-of-bounds access in semctl(2)

7.8HighCVSS 7.8EPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in p8, p12 and p2.

The GETALL and SETALL commands in semctl(2) recorded the number of semaphores in the target set, dropped the lock protecting the set, allocated a buffer sized for that count, and reacquired the lock. A sequence-number check was used to verify that the set had not been replaced in the interim, but the sequence number wraps after 0x8000 create/destroy cycles. By rapidly destroying and recreating semaphore sets at the same index, another process can cause the sequence number to wrap, allowing a set with a different number of semaphores to pass validation. The subsequent copy then reads or writes past the end of the allocated buffer. An unprivileged local user can trigger out-of-bounds reads and writes on kernel heap memory, potentially leading to privilege escalation.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
FreeBSD>=14.4-RELEASE <p8, >=15.0-RELEASE <p12, >=15.1-RELEASE <p2p8, p12, p2

Timeline

Every event on this vulnerability

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-58087 severity on Zeptric[![CVE-2026-58087](https://zeptric.io/badge/cve/CVE-2026-58087.svg)](https://zeptric.io/cve/CVE-2026-58087)