CVE-2026-99058 json
workqueue: Fix NULL current_pwq deref in chained work check
published 19d ago modified 12d ago also EUVD-2026-108724
- cvss
- —
- not scored
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 8%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- Linux Linux 7.3
- linux Debian 13 6.12.113-1
- linux Debian 14 7.2.11-1
debian advisories DEBIAN-CVE-2026-99058
- linux Ubuntu 26.10 7.3.0-10.10
- linux-aws Ubuntu 26.10 7.3.0-1004.4
- linux-gcp Ubuntu 26.10 7.3.0-1004.4
- linux-raspi Ubuntu 26.10 7.3.0-1004.4
- linux-riscv Ubuntu 26.10 7.3.0-10.10.1
- linux-oracle Ubuntu 26.10 7.3.0-1004.4
- linux-realtime Ubuntu 26.10 7.3.0-10.10.1
ubuntu advisories UBUNTU-CVE-2026-99058
Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
- kernel Azure Linux 3.0 6.6.161.1-1
azure linux advisories AZL-110945
Azure Linux vulnerability data, Copyright (c) Microsoft Corporation, from https://github.com/microsoft/AzureLinuxVulnerabilityData via OSV, under the MIT licence; changed: normalised to fixed package versions per release. MIT
- git.kernel.org/stable/c/73bec442f913855907b63225306dd162c18e5c71 commit
- git.kernel.org/stable/c/6877de2c75f0dd342099a1357856e6c8d474abc3 commit
- git.kernel.org/stable/c/54361e4924c2c52a501b74ef10217c32f45fccfa commit
- git.kernel.org/stable/c/3dc61af2998cfc7312d6e59bbdcd5eed074483f2 commit
- git.kernel.org/stable/c/729d576df89c7e4341e58c452f8890620a610ac2 commit
- git.kernel.org/stable/c/b12a25fb2b9d5dac80e419d695450cc17a51fdfd commit
- git.kernel.org/stable/c/1a2668682e998039a027796b236319b380078a6a commit
- git.kernel.org/stable/c/980db94e3eeefdd8a1c46f86412c33a7f7806f51 commit
Is CVE-2026-99058 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerVendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2026-99058 updated cvss 4.7
kernel: workqueue: Fix NULL current_pwq deref in chained work check
-
Red Hat Enterprise Linux 6 perf, kernel, python-perf, kernel-kdump, kernel-firmware, kernel-bootwrapper, +1 moreaffected: no fix planned “Out of support scope”
-
Red Hat Enterprise Linux 7 perf, kernel, bpftool, kernel-rt, python-perf, kernel-kdump, +8 more Red Hat Enterprise Linux 8 perf, kernel, bpftool, kernel-rt, kernel-core, kernel-tools, +29 more Red Hat Enterprise Linux 9 rv, perf, rtla, kernel, bpftool, libperf, +83 more Red Hat Enterprise Linux 10 kernel Red Hat OpenShift Container Platform 4 openshift/ose-rhel-coreos-8, openshift/ose-rhel-coreos-9 Red Hat OpenShift Container Platform 5 openshift/ose-rhel-coreos-9affected: no fix available “Fix deferred”
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
0.19% chance of exploitation in the next 30 days, higher than 8% of all scored CVEs (FIRST EPSS, 2026-11-11).
Affected products
- Linux Linux
Classification
- Technology feeds
References
- git.kernel.org /stable/c/73bec442f913855907b63225306dd162c18e5c71
- git.kernel.org /stable/c/6877de2c75f0dd342099a1357856e6c8d474abc3
- git.kernel.org /stable/c/54361e4924c2c52a501b74ef10217c32f45fccfa
- git.kernel.org /stable/c/3dc61af2998cfc7312d6e59bbdcd5eed074483f2
- git.kernel.org /stable/c/729d576df89c7e4341e58c452f8890620a610ac2
- git.kernel.org /stable/c/b12a25fb2b9d5dac80e419d695450cc17a51fdfd
- git.kernel.org /stable/c/1a2668682e998039a027796b236319b380078a6a
- git.kernel.org /stable/c/980db94e3eeefdd8a1c46f86412c33a7f7806f51
Sources
- CVE List CVE-2026-99058
- NVD CVE-2026-99058
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.