PT-2026-122035

CVE-2026-99058

·

Published

2026-10-23

·

Updated

2026-10-23

Description by

Score
N/A
Not available

No severity ratings or metrics are available. When they are, we'll update the corresponding info on the page.

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.
Vendors
Affected products
Related identifiers
Found an issue in the description? Have something to add? Feel free to write us 👾