CVE-2026-99058: Linux kernel · workqueue: Fix NULL current_pwq deref in chained work check
Affects Linux kernelSource GCVE Database
Not known to be exploited.
Data as of 28 Oct 2026, 01:43 UTC
Rated by Threat Radar · CVSS not yet scored by NVD
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
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Ubuntu 26.10linuxpkg:deb/ubuntu/linux?arch=source&distro=stonkingOther threats | Affected
| Fixed in– |
Ubuntu 26.10linux-awspkg:deb/ubuntu/linux-aws?arch=source&distro=stonkingOther threats | Affected
| Fixed in– |
Ubuntu 26.10linux-azurepkg:deb/ubuntu/linux-azure?arch=source&distro=stonkingOther threats | Affected
| Fixed in– |
Ubuntu 26.10linux-azure-fdepkg:deb/ubuntu/linux-azure-fde?arch=source&distro=stonkingOther threats | Affected
| Fixed in– |
Ubuntu 26.10linux-gcppkg:deb/ubuntu/linux-gcp?arch=source&distro=stonkingOther threats | Affected
| Fixed in– |
Ubuntu 26.10linux-oraclepkg:deb/ubuntu/linux-oracle?arch=source&distro=stonkingOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
A fix for this issue has been implemented in the Linux kernel. Users should apply the official kernel updates that include this patch to prevent the NULL pointer dereference. No additional mitigation steps are required beyond updating to a fixed kernel version.
Description
A vulnerability in the Linux kernel's workqueue subsystem could cause a NULL pointer dereference when checking chained work. This occurs because the worker's current_pwq pointer may be NULL outside of work-item execution, leading to a fault before a warning is emitted. The issue has been fixed by adding a guard to ensure current_pwq is valid before the chained-work test.
References
- ubuntu.com/security/CVE-2026-99058 (opens in a new tab)
- cve.org/CVERecord?id=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)