Heap out-of-bounds access in semop(2)
Summary
| CVE | CVE-2026-58098 |
|---|---|
| State | PUBLISHED |
| Assigner | freebsd |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2026-10-15 07:18:02 UTC |
| Updated | 2026-10-16 04:18:32 UTC |
| Description | When semop(2) 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 enough semaphore sets are created and destroyed in the same table slot while a caller is blocked, the counter wraps around, and semop(2) may falsely conclude that the original set still exists. The subsequent access to a semaphore within the set may then be out of bounds. An unprivileged local user can trigger an out-of-bounds access on kernel heap memory, potentially leading to privilege escalation. |
Risk And Classification
Problem Types: CWE-787 | CWE-787 CWE-787: Out-of-bounds Write
Vendor Declared Affected Products
| Source | Vendor | Product | Version | Platforms |
|---|---|---|---|---|
| CNA | FreeBSD | FreeBSD | affected 15.1-RELEASE p4 release | Not specified |
| CNA | FreeBSD | FreeBSD | affected 15.0-RELEASE p14 release | Not specified |
| CNA | FreeBSD | FreeBSD | affected 14.5-RELEASE p1 release | Not specified |
| CNA | FreeBSD | FreeBSD | affected 14.4-RELEASE p10 release | Not specified |
References
| Reference | Source | Link | Tags |
|---|---|---|---|
| security.freebsd.org/advisories/FreeBSD-SA-26:64.sysvsem.asc | [email protected] | security.freebsd.org | |
| CVE Program record | CVE.ORG | www.cve.org | canonical |
| NVD vulnerability detail | NVD | nvd.nist.gov | canonical, analysis |
Vendor Comments And Credit
Discovery Credit
CNA: Reo Shiseki (en)
CNA: Andrew Griffiths (en)
There are currently no legacy QID mappings associated with this CVE.