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.
Fix
Patch, vendor advisory and mitigation references on NVD 1
Every line above is quoted from NVD, CISA, Microsoft, the vendor's own advisory or DISA; nothing is generated.
Change history 6
- Cpes+4 CPE criteria (now 4)NVD modified 2026-10-19 21:02
- StatusUndergoing Analysis → AnalyzedNVD modified 2026-10-19 21:02
- CVSS7.0 (v3.1, CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H)NVD modified 2026-10-19 15:17
- StatusAwaiting Analysis → Undergoing AnalysisNVD modified 2026-10-16 04:18
- StatusReceived → Awaiting AnalysisNVD modified 2026-10-15 16:17
- First seenunscoredNVD modified 2026-10-15 07:18
Affected (CPE criteria) 4
cpe:2.3:o:freebsd:freebsd:15.1:-:*:*:*:*:*:*cpe:2.3:o:freebsd:freebsd:15.1:p1:*:*:*:*:*:*cpe:2.3:o:freebsd:freebsd:15.1:p2:*:*:*:*:*:*cpe:2.3:o:freebsd:freebsd:15.1:p3:*:*:*:*:*:*