Local root escalation via semaphore use-after-free
Published Jun 25, 2026 · Updated Jun 25, 2026
Use-after-free in OpenBSD through 7.9 allows local users to escalate privileges to root through the System V semaphore subsystem. The kernel keeps using a semaphore object after tsleep in sys_semget() without retaining a reference, so another context can free it during the switch. Exploitation requires local syscall access and winning this race; success grants root-level control of the affected system.
Summary
What happened
Use-after-free in OpenBSD through 7.9 allows local users to escalate privileges to root through the System V semaphore subsystem. The kernel keeps using a semaphore object after tsleep in sys_semget() without retaining a reference, so another context can free it during the switch. Exploitation requires local syscall access and winning this race; success grants root-level control of the affected system.
The record
- CVE
- CVE-2026-57589
- Published
- Jun 25, 2026
- Updated
- Jun 25, 2026
- Vendor
- OpenBSD Project
- Product
- OpenBSD
- Classifications
- CWE-416, T1068
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 25, 2026CVE publishedPublication date reported by the CVE source.
- Jun 25, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <=7.9
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo