CVE-2026-58098

Heap out-of-bounds access in semop(2)

  • High 8.4

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.

Key facts

Published
15 Oct 2026
Last changed
16 Oct 2026
Assigned by
freebsd
EPSS
0.114% likely to be exploited in the next 30 days, higher than 1.501% of CVEs (scores for 18 Nov 2026)
SSVC (CISA)
Exploitation: none; Automatable: no; Technical impact: total

Severity scores

Each score is shown as its source gave it. They are not averaged or merged.

  • 8.4CVSS 3.1, Highfrom CISA (ADP container)CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Historical context and remediation

This reference retains the original CVE publication date. A recent record update does not mean a new attack occurred.

No separately sourced impact summary is available on this page yet. Consult the description, version data and dated exploitation evidence.

No explicit remediation statement is available on this page yet. Consult the original record and vendor references before choosing a fix.

Version statuses below come from the CNA. An “unaffected” version is not necessarily a currently supported release or proof of a patch date. EPSS is a dated risk estimate, not a count of historical attacks.

Read the original CVE record.

Affected products

VendorProductVersions
FreeBSDFreeBSD
  • Default status: unknown
  • 15.1-RELEASE up to but excluding p4 (affected)
  • 15.0-RELEASE up to but excluding p14 (affected)
  • 14.5-RELEASE up to but excluding p1 (affected)
  • 14.4-RELEASE up to but excluding p10 (affected)

Timeline

  1. 15 Oct 2026 Published

Weakness

References