CVE-2026-99058: Linux kernel · workqueue: Fix NULL current_pwq deref in chained work check
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in b12a25fb2b9d5dac80e419d695450cc17a51fdfd : update Linux kernel when convenient.
Data as of 26 Oct 2026, 14:18 UTC
Rated Medium by Threat Radar's AI analysis · CVSS not yet scored by NVD
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 7% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in b12a25fb2b9d5dac80e419d695450cc17a51fdfd, 980db94e3eeefdd8a1c46f86412c33a7f7806f51, 729d576df89c7e4341e58c452f8890620a610ac2 +2
Exploitation evidence
Disclosed: evidence found.
CVE published 23 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 26 Oct 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in– |
AI-suggested
A fix is available and has been applied in the specified commits. Users should update their Linux kernel to versions including these fixes to prevent the NULL pointer dereference. No additional mitigation is required beyond applying the patch.
Description
A vulnerability in the Linux kernel workqueue subsystem involving a NULL pointer dereference in the chained work check has been fixed. The issue occurs because current_wq_worker() indicates a kworker but does not guarantee that the worker is executing a work item, leading to a possible NULL dereference of worker->current_pwq. This flaw can cause a fault when is_chained_work() is called during queueing on a draining or destroying workqueue. The fix adds a guard to ensure worker->current_pwq is valid before the chained-work test proceeds.
References
- git.kernel.org/stable/c/3dc61af2998cfc7312d6e59bbdcd5eed074483f2 (opens in a new tab)
- git.kernel.org/stable/c/729d576df89c7e4341e58c452f8890620a610ac2 (opens in a new tab)
- git.kernel.org/stable/c/b12a25fb2b9d5dac80e419d695450cc17a51fdfd (opens in a new tab)
- git.kernel.org/stable/c/1a2668682e998039a027796b236319b380078a6a (opens in a new tab)
- git.kernel.org/stable/c/980db94e3eeefdd8a1c46f86412c33a7f7806f51 (opens in a new tab)