CVE-2026-58099

Memory safety bugs in kqueue copy-on-fork implementation

Published Oct 15, 2026 CVSS 3.1 · 7 High EPSS < 1% KEV · Not listed
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.

Remediation

No solution or workaround provided in the CVE record

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
CPEs 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:*:*:*:*:*:*
Type Values Removed Values Added
Metrics cvssV3_1

{'score': 7, 'vector': 'CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H'}

Type Values Removed Values Added
First Time appeared Freebsd
Freebsd freebsd
Vendors & Products Freebsd
Freebsd freebsd
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'total'}, 'version': '2.0.3'}

Type Values Removed Values Added
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.
Title Memory safety bugs in kqueue copy-on-fork implementation
Weaknesses CWE-362
CWE-416
References
Weaknesses

Sources

Status
PUBLISHED
Assigner
freebsd
Published
Updated
Oct 19, 2026, 2:10 PM
Reserved
Jun 29, 2026, 1:40 AM
Status
Analyzed
Published
Oct 15, 2026, 7:18 AM
Modified
Oct 19, 2026, 9:02 PM