io-wq: order the exit bit against worker creation task work
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 67da3eec264aeb67835886720243ae2dc1463315, Kernel 5.15.224, Kernel 0d81cdd433b0a96c5275c01b8172e0b1f71dd595 and 6 more.
In the Linux kernel, the following vulnerability has been resolved: io-wq: order the exit bit against worker creation task work io_wq_exit_workers() cancels task work for queued worker creation with task_work_cancel_match(). That has a plain load of task->task_works. io_queue_worker_create() adds the new entry and tests IO_WQ_BIT_EXIT to cancel it if the workqueue is already on its way out. That must be ordered. task_work_add() has a full barrier via cmpxchg(). But io_wq_exit_start() sets the bit with set_bit() which doesn't have any memory ordering. So afaict, on weakly ordered architectures the exiting task may load task_works before the store of the bit is visible. The other side tests the bit before the store is visible as well. So the entry remains queued with worker_refs and the exiting task waits on worker_done indefinitely. If the task still has rings then io_uring_del_tctx_node() provides the barrier via test_and_set_bit() in io_wq_set_exit_on_idle(). When it has closed all rings though that barrier is gone. Add the barrier after the set_bit().
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | =5.16, >=4b4e5bbf9386d4ec21d91c0cb0fd60b9bba778ec <67da3eec264aeb67835886720243ae2dc1463315, >=5.15.11 <5.15.224, >=71a85387546e50b1a37b0fa45dadcae3bfb35cf6 <0d81cdd433b0a96c5275c01b8172e0b1f71dd595, >=71a85387546e50b1a37b0fa45dadcae3bfb35cf6 <0e5663856b69219ef2f02e04bac9f5c5be19718a, >=71a85387546e50b1a37b0fa45dadcae3bfb35cf6 <1432d881d99584105122760133caeff1dce7a9f7, >=71a85387546e50b1a37b0fa45dadcae3bfb35cf6 <31fc780b75b278d37700373d54a99fdb4117fdd6, >=71a85387546e50b1a37b0fa45dadcae3bfb35cf6 <6cf012a4d5e461c788ecc9dbed67adc31a142644, >=71a85387546e50b1a37b0fa45dadcae3bfb35cf6 <75395db7a9b40a2e826c838e648fef8ed1a2d174, >=71a85387546e50b1a37b0fa45dadcae3bfb35cf6 <a63c752157eacf49f628359822666b32503d194a | 67da3eec264aeb67835886720243ae2dc1463315, 5.15.224, 0d81cdd433b0a96c5275c01b8172e0b1f71dd595, 0e5663856b69219ef2f02e04bac9f5c5be19718a, 1432d881d99584105122760133caeff1dce7a9f7, 31fc780b75b278d37700373d54a99fdb4117fdd6, 6cf012a4d5e461c788ecc9dbed67adc31a142644, 75395db7a9b40a2e826c838e648fef8ed1a2d174, a63c752157eacf49f628359822666b32503d194a |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket