workqueue: Put the pwq after detaching the rescuer from the pool
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
6.12.166.13.46.14In the Linux kernel, the following vulnerability has been resolved:
workqueue: Put the pwq after detaching the rescuer from the pool
The commit 68f83057b913("workqueue: Reap workers via kthread_stop() and remove detach_completion") adds code to reap the normal workers but mistakenly does not handle the rescuer and also removes the code waiting for the rescuer in put_unbound_pool(), which caused a use-after-free bug reported by Cheung Wall.
To avoid the use-after-free bug, the pool’s reference must be held until the detachment is complete. Therefore, move the code that puts the pwq after detaching the rescuer from the pool.
From the CVE record · Linux
The Linux kernel workqueue code can release a pool reference before its rescuer has finished detaching, causing a use-after-free. The input does not specify how an attacker could trigger the bug, its impact, or whether exploitation requires local access, authentication, or user interaction.
Engineers running the Linux kernel should check their versions; affected versions are not specified in the input.