CVE-2026-58099
Undergoing Analysis Undergoing Analysis - In Progress

Use-After-Free in FreeBSD Kqueue Due to Improper Marker Knote Handling

Vulnerability report for CVE-2026-58099, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-10-15

Last updated on: 2026-10-16

Assigner: FreeBSD

Description

When copying knotes from a parent kqueue to a child, the copy code did not correctly exclude marker knotes (used internally to track list traversal position) before marking them as in-flux and releasing the kqueue lock. If another thread freed a marker while the lock was dropped, the subsequent in-flux decrement operated on freed memory. An unprivileged local user may be able to exploit these races to escalate privileges.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-10-15
Last Modified
2026-10-16
Generated
2026-10-19
AI Q&A
2026-10-15
EPSS Evaluated
2026-10-18
NVD
EUVD

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
FreeBSD FreeBSD 15.1-RELEASE

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-416 The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory "belongs" to the code that operates on the new pointer.
CWE-362 The product contains a concurrent code sequence that requires temporary, exclusive access to a shared resource, but a timing window exists in which the shared resource can be modified by another code sequence operating concurrently.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability involves a race condition in FreeBSD's kqueue copy-on-fork implementation. When copying knotes from a parent kqueue to a child process, marker knotes used for internal list traversal were not properly excluded. This led to freed memory being accessed due to incorrect synchronization, potentially allowing an unprivileged local user to escalate privileges.

Detection Guidance

This vulnerability is specific to FreeBSD systems and involves race conditions in the kqueue implementation. Detection requires checking FreeBSD version and applying patches. No direct commands detect active exploitation, but verify system version and patch status with: freebsd-version and pkg audit -F.

Impact Analysis

An unprivileged local user could exploit this vulnerability to escalate their privileges on a FreeBSD system running version 15.1. This could allow them to gain unauthorized access to sensitive data or perform actions beyond their intended permissions.

Compliance Impact

This vulnerability does not directly affect compliance with standards like GDPR or HIPAA as it is a local privilege escalation issue in FreeBSD's kqueue implementation. Compliance impacts would only occur if the vulnerability enabled unauthorized access to sensitive data or systems, which is not described in the provided context.

Mitigation Strategies

Immediately upgrade FreeBSD to a corrected version of 15.1 or later using pkg update && pkg upgrade, freebsd-update fetch install, or apply source code patches. Ensure the system is rebooted after applying updates to activate the fixes.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-58099. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart