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.
CVE-2026-58099
Primary source · Revision 1
Imported from structured advisory data. Source references identify upstream records or fields; verify affected versions and your deployed configuration.
Security context
Source reference: cve:CVE-2026-58099
FreeBSD
Source reference: /containers/cna/affected/0/product
- Affected versions
- Not stated in this record
- Fixed versions
- Not stated in this record
- Prerequisites
- Not stated in this record
Structured affected-version data
Original package identities and version rules from this source.
[
{
"vendor": "FreeBSD",
"modules": [
"kqueue"
],
"product": "FreeBSD",
"versions": [
{
"status": "affected",
"version": "15.1-RELEASE",
"lessThan": "p4",
"versionType": "release"
}
],
"defaultStatus": "unknown"
}
]- Related CVEs
- CVE-2026-58099
Source reference:
/cveMetadata/cveId
Publisher severity
No explicit severity was provided.
- Event
- #38872 · Revision 1
- Added to Heist Feed
- Publisher date