CVE-2026-58099Memory safety bugs in kqueue copy-on-fork implementation
Updated under an hour ago ()
Does this affect you?
It affects FreeBSD. Add what you run to find out whether that includes you.
No exploitation reported and no EPSS estimate yet.
Do this next
Free account, 1 product
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
- Not yet scored
- Weakness (CWE)
- CWE-362, CWE-416
- Known exploited
- Not in CISA's KEV catalog
- EPSS (exploitation in the next 30 days)
- Not loaded for this CVE
- Assigned by
- freebsd
- NVD analysis
- Undergoing Analysis
- Record last updated
- Oct 16, 2026
- First seen by InfoSec Signals
- Oct 15, 2026
Affected products
FreeBSD FreeBSD freebsd:freebsd (from the name) | from 15.1-RELEASE before p4 | CNA record |
References
- https://security.freebsd.org/advisories/FreeBSD-SA-26:65.kqueue.ascvendor-advisory
The CVE record on cve.org NVD's entry
The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.