Memory safety bugs in kqueue copy-on-fork implementation
Summary
| CVE | CVE-2026-58099 |
|---|---|
| State | PUBLISHED |
| Assigner | freebsd |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2026-10-15 07:18:02 UTC |
| Updated | 2026-10-16 04:18:32 UTC |
| 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. |
Risk And Classification
Problem Types: CWE-362 | CWE-416 | CWE-362 CWE-362: Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition') | CWE-416 CWE-416: Use After Free
Vendor Declared Affected Products
References
| Reference | Source | Link | Tags |
|---|---|---|---|
| security.freebsd.org/advisories/FreeBSD-SA-26:65.kqueue.asc | [email protected] | security.freebsd.org | |
| CVE Program record | CVE.ORG | www.cve.org | canonical |
| NVD vulnerability detail | NVD | nvd.nist.gov | canonical, analysis |
Vendor Comments And Credit
Discovery Credit
CNA: Reo Shiseki (en)
CNA: Mark Johnston (en)
There are currently no legacy QID mappings associated with this CVE.