io_uring: check if iowq is killed before queuing
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 |
|
|
In the Linux kernel, the following vulnerability has been resolved:
io_uring: check if iowq is killed before queuing
task work can be executed after the task has gone through io_uring termination, whether it's the final task_work run or the fallback path. In this case, task work will find ->io_wq being already killed and null'ed, which is a problem if it then tries to forward the request to io_queue_iowq(). Make io_queue_iowq() fail requests in this case.
Note that it also checks PF_KTHREAD, because the user can first close a DEFER_TASKRUN ring and shortly after kill the task, in which case ->iowq check would race.
From the CVE record · Linux
In the Linux kernel, io_uring task work can try to queue a request after its io_wq has been killed and cleared. This can occur after io_uring termination, including when a user closes a DEFER_TASKRUN ring and then kills the task; the input does not specify a further impact.
Engineers running the Linux kernel should check their versions; the affected versions are not specified.