CVE-2026-99058: Linux kernel · workqueue: Fix NULL current_pwq deref in chained work check
Source GCVE Database
Not known to be exploited · fixed in b12a25fb2b9d5dac80e419d695450cc17a51fdfd : update Linux kernel when convenient.
Data as of 26 Oct 2026, 12:55 UTC
Rated by Threat Radar · 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– |
Description
In the Linux kernel, the following vulnerability has been resolved: workqueue: Fix NULL current_pwq deref in chained work check current_wq_worker() only tells us that %current is a kworker. It does not guarantee that the worker is currently executing a work item, as worker->current_pwq is populated only while process_one_work() is running the work function. is_chained_work() can be reached while queueing on a draining or destroying workqueue. If a kworker outside work-item execution reaches that path, current_wq_worker() returns a worker but worker->current_pwq is NULL, and the chained-work test can fault before it emits the intended warning. Guard the chained-work test with worker->current_pwq. A kworker without current_pwq is not executing work on the target workqueue, so the helper should return false and let the draining/destroying warning fire.
References
- nvd.nist.gov/vuln/detail/CVE-2026-99058 (opens in a new tab)
- git.kernel.org/stable/c/1a2668682e998039a027796b236319b380078a6a (opens in a new tab)
- 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/980db94e3eeefdd8a1c46f86412c33a7f7806f51 (opens in a new tab)
- git.kernel.org/stable/c/b12a25fb2b9d5dac80e419d695450cc17a51fdfd (opens in a new tab)