Vulnerability Monitor

The vendors, products, and vulnerabilities you care about

CVE-2026-58098


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.


Security Impact Summary

This vulnerability carries a HIGH severity rating with a CVSS v3.1 score of 8.4, requiring local system access to exploit with relatively low complexity without requiring user interaction and does not require pre-existing privileges . The vulnerability impacts confidentiality (data exposure), integrity (unauthorized modifications), and availability (service disruption) for affected systems. Impacting 1 product from freebsd organizations running these solutions should prioritize assessment and patching.

Historical Context

Reported in 2026, this vulnerability emerged during an era marked by increased sophistication in supply chain attacks, cloud infrastructure vulnerabilities, and software-as-a-service (SaaS) security challenges. Security practices during this period emphasized zero-trust architectures, container security, and API protection.


Published

2026-10-15T07:18:02.250

Last Modified

2026-10-19T21:05:21.253

Status

Analyzed

Source

[email protected]

Severity

CVSSv3.1: 8.4 (HIGH)

Weaknesses
  • Type: Secondary
    CWE-787

Affected Vendors & Products
Type Vendor Product Version/Range Vulnerable?
Operating System freebsd freebsd 14.4 Yes
Operating System freebsd freebsd 14.4 Yes
Operating System freebsd freebsd 14.4 Yes
Operating System freebsd freebsd 14.4 Yes
Operating System freebsd freebsd 14.4 Yes
Operating System freebsd freebsd 14.4 Yes
Operating System freebsd freebsd 14.4 Yes
Operating System freebsd freebsd 14.4 Yes
Operating System freebsd freebsd 14.4 Yes
Operating System freebsd freebsd 14.4 Yes
Operating System freebsd freebsd 14.5 Yes
Operating System freebsd freebsd 15.0 Yes
Operating System freebsd freebsd 15.0 Yes
Operating System freebsd freebsd 15.0 Yes
Operating System freebsd freebsd 15.0 Yes
Operating System freebsd freebsd 15.0 Yes
Operating System freebsd freebsd 15.0 Yes
Operating System freebsd freebsd 15.0 Yes
Operating System freebsd freebsd 15.0 Yes
Operating System freebsd freebsd 15.0 Yes
Operating System freebsd freebsd 15.0 Yes
Operating System freebsd freebsd 15.0 Yes
Operating System freebsd freebsd 15.0 Yes
Operating System freebsd freebsd 15.0 Yes
Operating System freebsd freebsd 15.0 Yes
Operating System freebsd freebsd 15.1 Yes
Operating System freebsd freebsd 15.1 Yes
Operating System freebsd freebsd 15.1 Yes
Operating System freebsd freebsd 15.1 Yes

References

How SecUtils Interprets This CVE

SecUtils normalizes and enriches National Vulnerability Database (NVD) records by standardizing vendor and product identifiers, aggregating vulnerability metadata from both NVD and MITRE sources, and providing structured context for security teams. For freebsd's affected products, we extract Common Platform Enumeration (CPE) data, Common Weakness Enumeration (CWE) classifications, CVSS severity metrics, and reference data to enable rapid vulnerability prioritization and asset correlation. This record contains no exploit code, proof-of-concept instructions, or attack methodologies—only defensive intelligence necessary for patch management, risk assessment, and security operations.