Skip to main content
VulnerabilityPublished

CVE-2026-58083: 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

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-58083· High 8.4

Not known to be exploited · CVSS 8.4 High.

Data as of 18 Nov 2026, 20:25 UTC

CVSS 3.1 base score
8.4High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.1% chance of exploitation in 30 days – higher than 6% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 19 Aug 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 18 Nov 2026.

What to do

AI-suggested

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.

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.

References

Community reviews

Loading reviews…