While the kernel was copying knotes during fork, a knote with a timer-based filter could fire and be enqueued on the kqueue's active list before the copy was complete. The copy routine did not account for this and could enqueue the new knote a second time, corrupting the active list. In addition, the copy routine did not hold the appropriate locks while reading knote state, allowing further races.
An unprivileged local user can trigger a use-after-free in the kernel, potentially leading to privilege escalation.
Metrics
Affected Vendors & Products
No data.
No data.
No data.
No data.
References
History
Wed, 19 Aug 2026 07:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | While the kernel was copying knotes during fork, a knote with a timer-based filter could fire and be enqueued on the kqueue's active list before the copy was complete. The copy routine did not account for this and could enqueue the new knote a second time, corrupting the active list. In addition, the copy routine did not hold the appropriate locks while reading knote state, allowing further races. An unprivileged local user can trigger a use-after-free in the kernel, potentially leading to privilege escalation. | |
| Title | Use-after-free in kqueue copy-on-fork | |
| Weaknesses | CWE-416 | |
| References |
|
MITRE
Status: PUBLISHED
Assigner: freebsd
Published:
Updated: 2026-08-19T07:33:21.096Z
Reserved: 2026-06-29T01:40:17.498Z
Link: CVE-2026-58083
Vulnrichment
No data.
NVD
Status : Received
Published: 2026-08-19T08:17:12.470
Modified: 2026-08-19T08:17:12.470
Link: CVE-2026-58083
Redhat
No data.
OpenCVE Enrichment
No data.