PoC Monitor
← All CVEs
CVE-2026-58098published 15 Oct 2026 06:15 UTCData: JSON · API

FreeBSD

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.

First public PoC None yetno public PoC found
Public PoCs00 on GitHub
CVSS8.4high · scored by CISA ADP · CWE-787
CISA KEV Not listednot known exploited

Affected versions and mitigation

From the CVE record and the vendor's references.

Affected

FreeBSD FreeBSD
  • >= 15.1-RELEASE, < p4
  • >= 15.0-RELEASE, < p14
  • >= 14.5-RELEASE, < p1
  • >= 14.4-RELEASE, < p10

Fixed in p4, p14, p1, p10

Mitigation

Upgrade FreeBSD to p4 or p14 or p1 or p10 or later.

References

Timeline

Days relative to CVE publication
-2t=0+2+4+6+8CVE published15 Oct 2026 · t = 0

No public PoC found yet; not in CISA KEV.

PoC repositories

Found on GitHub.

1 informational

Informational 1
RepositoryCreatedStarsAssessment
adri22235/ps4-13xx-research 11 Aug 2026 −64 d 2 Informational · list

Only PoCs count toward the first-PoC date and the characteristics below. Do not run PoC code from unknown sources.