CVE-2026-99058: workqueue: Fix NULL current_pwq deref in chained work check

Published Oct 23, 2026
·
Updated

In the Linux kernel, the following vulnerability has been resolved:

workqueue: Fix NULL currentpwq deref in chained work check

currentwqworker() only tells us that %current is a kworker. It does not guarantee that the worker is currently executing a work item, as worker->currentpwq is populated only while processonework() is running the work function.

ischainedwork() can be reached while queueing on a draining or destroying workqueue. If a kworker outside work-item execution reaches that path, currentwqworker() returns a worker but worker->currentpwq is NULL, and the chained-work test can fault before it emits the intended warning.

Guard the chained-work test with worker->currentpwq. A kworker without currentpwq is not executing work on the target workqueue, so the helper should return false and let the draining/destroying warning fire.

Affected Software

1 affected component
Linux Linux kernel

Event History

Oct 23, 2026
CVE Published
via MITRE·12:22 PM
Data Sourced
via MITRE·12:22 PM
Description

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203