FreeBSD
Heap out-of-bounds access in semctl(2)
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 versions and mitigation
From the CVE record and the vendor's references.Affected
- >= 15.1-RELEASE, < p2
- >= 15.0-RELEASE, < p12
- >= 14.4-RELEASE, < p8
Fixed in p2, p12, p8
Mitigation
Upgrade FreeBSD to p2 or p12 or p8 or later.
References
- Vendor advisory security.freebsd.org/advisories/FreeBSD-SA-26:54.sysvsem…
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.1 informational
Informational 1
| Repository | Created | Stars | Assessment |
|---|---|---|---|
| adri22235/ps4-13xx-research | 11 Aug 2026 −7.5 d | 2 | Informational · list |
Only PoCs count toward the first-PoC date and the characteristics below. Do not run PoC code from unknown sources.