While the kernel was copying knotes during fork, a knote with a timer-based filter could fire and be enqueued on the kqueue's active list before the… (CVE-2026-58083)
A kernel vulnerability exists where during the fork operation, a timer-based knote can be enqueued twice on the kqueue's active list due to improper handling in the copy routine. This leads to corruption of the active list and introduces race conditions because appropriate locks are not held. An unprivileged local user can exploit this use-after-free condition to potentially escalate privileges.
AI Analysis
Technical Summary
The vulnerability arises from the kernel's handling of knotes during the fork process. Specifically, if a knote with a timer-based filter fires while the kernel is copying knotes, it can be enqueued on the kqueue's active list before the copy completes. The copy routine does not account for this scenario and may enqueue the new knote a second time, corrupting the active list. Additionally, the copy routine fails to hold the necessary locks when reading knote state, allowing race conditions. This use-after-free vulnerability can be triggered by an unprivileged local user, potentially leading to privilege escalation.
Potential Impact
An unprivileged local attacker can exploit this vulnerability to cause a use-after-free condition in the kernel, which may result in privilege escalation. The corruption of the kqueue's active list and race conditions can compromise kernel stability and security, potentially allowing the attacker to gain higher privileges or execute arbitrary code in kernel context.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, restrict unprivileged local access to affected systems and monitor for suspicious local activity related to kqueue usage. Avoid running untrusted code locally that could trigger this vulnerability.
While the kernel was copying knotes during fork, a knote with a timer-based filter could fire and be enqueued on the kqueue's active list before the… (CVE-2026-58083)
Description
A kernel vulnerability exists where during the fork operation, a timer-based knote can be enqueued twice on the kqueue's active list due to improper handling in the copy routine. This leads to corruption of the active list and introduces race conditions because appropriate locks are not held. An unprivileged local user can exploit this use-after-free condition to potentially escalate privileges.
CVSS v3.1
Score 8.4high
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The vulnerability arises from the kernel's handling of knotes during the fork process. Specifically, if a knote with a timer-based filter fires while the kernel is copying knotes, it can be enqueued on the kqueue's active list before the copy completes. The copy routine does not account for this scenario and may enqueue the new knote a second time, corrupting the active list. Additionally, the copy routine fails to hold the necessary locks when reading knote state, allowing race conditions. This use-after-free vulnerability can be triggered by an unprivileged local user, potentially leading to privilege escalation.
Potential Impact
An unprivileged local attacker can exploit this vulnerability to cause a use-after-free condition in the kernel, which may result in privilege escalation. The corruption of the kqueue's active list and race conditions can compromise kernel stability and security, potentially allowing the attacker to gain higher privileges or execute arbitrary code in kernel context.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, restrict unprivileged local access to affected systems and monitor for suspicious local activity related to kqueue usage. Avoid running untrusted code locally that could trigger this vulnerability.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-j94h-9p69-vhvm
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-58083"]
- Ecosystems
- []
- Database Specific Severity
- HIGH
- Cvss Version
- 3.1
Threat ID: 6a85b49bacd9273b49250292
Added to database: 08/19/2026, 13:50:19 UTC
Last enriched: 08/19/2026, 13:52:22 UTC
Last updated: 08/19/2026, 13:52:22 UTC
Views: 1
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.