FreeBSD
Memory safety bugs in kqueue copy-on-fork implementation
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.
First public PoC
None yetno public PoC found
Public PoCs00 on GitHub
CVSS7.0high · scored by CISA ADP · CWE-362
CISA KEV
Not listednot known exploited
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
FreeBSD FreeBSD
- >= 15.1-RELEASE, < p4
Fixed in p4
Mitigation
Upgrade FreeBSD to p4 or later.
References
- Vendor advisory security.freebsd.org/advisories/FreeBSD-SA-26:65.kqueue.…
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.No PoC repositories found yet.