Heap out-of-bounds access in semop(2)
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.
CVE-2026-58098
Primary source · Revision 1
Imported from structured advisory data. Source references identify upstream records or fields; verify affected versions and your deployed configuration.
Security context
Source reference: cve:CVE-2026-58098
FreeBSD
Source reference: /containers/cna/affected/0/product
- Affected versions
- Not stated in this record
- Fixed versions
- Not stated in this record
- Prerequisites
- Not stated in this record
Structured affected-version data
Original package identities and version rules from this source.
[
{
"vendor": "FreeBSD",
"modules": [
"sysvsem"
],
"product": "FreeBSD",
"versions": [
{
"status": "affected",
"version": "15.1-RELEASE",
"lessThan": "p4",
"versionType": "release"
},
{
"status": "affected",
"version": "15.0-RELEASE",
"lessThan": "p14",
"versionType": "release"
},
{
"status": "affected",
"version": "14.5-RELEASE",
"lessThan": "p1",
"versionType": "release"
},
{
"status": "affected",
"version": "14.4-RELEASE",
"lessThan": "p10",
"versionType": "release"
}
],
"defaultStatus": "unknown"
}
]- Related CVEs
- CVE-2026-58098
Source reference:
/cveMetadata/cveId
Publisher severity
No explicit severity was provided.
- Event
- #32491 · Revision 1
- Added to Heist Feed
- Publisher date