An unprivileged local user may be able to exploit these races to escalate privileges.
No advisories yet.
Solution
No solution given by the vendor.
Workaround
No workaround given by the vendor.
Sat, 17 Oct 2026 19:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Freebsd
Freebsd freebsd |
|
| Vendors & Products |
Freebsd
Freebsd freebsd |
Fri, 16 Oct 2026 15:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
Thu, 15 Oct 2026 06:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| 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. | |
| Title | Memory safety bugs in kqueue copy-on-fork implementation | |
| Weaknesses | CWE-362 CWE-416 |
|
| References |
|
Projects
Sign in to view the affected projects.
Status: PUBLISHED
Assigner: freebsd
Published:
Updated: 2026-10-16T14:18:49.631Z
Reserved: 2026-06-29T01:40:17.499Z
Link: CVE-2026-58099
Updated: 2026-10-16T14:17:43.395Z
Status : Undergoing Analysis
Published: 2026-10-15T07:18:02.373
Modified: 2026-10-16T15:17:32.733
Link: CVE-2026-58099
No data.
OpenCVE Enrichment
Updated: 2026-10-17T19:00:13Z