io_uring: free the task context after a grace period
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 953174dcb862a7a364efdb65e178dcd3aea5562e, Kernel 9f5315d3f4368590c9fe06d4313b7247470bcf15 and Kernel 7.3.2.
In the Linux kernel, the following vulnerability has been resolved: io_uring: free the task context after a grace period A task other than the owner can free a request, io_ring_exit_work() running the local task_work of a DEFER_TASKRUN ring for example, or io_do_iopoll() reaping completions. io_put_task() then takes the else branch: percpu_counter_sub(&tctx->inflight, 1); if (unlikely(atomic_read(&tctx->in_cancel))) wake_up(&tctx->wait); put_task_struct(tctx->task); The first line is what lets the owner leave io_uring_cancel_generic(), and on exec it frees the tctx right after. Nothing holds that off for the remaining three lines, the task reference only covers a tctx freed along with the task_struct. It used to work out because io_uring_del_tctx_node() took the uring_lock that the freeing side holds across io_put_task(), until that moved to tctx_lock. Free the tctx with kfree_rcu(), and enter an RCU read section in io_put_task() before the count is dropped.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | =6.19, >=5623eb1ed035f01dfa620366a82b667545b10c82 <953174dcb862a7a364efdb65e178dcd3aea5562e, >=5623eb1ed035f01dfa620366a82b667545b10c82 <9f5315d3f4368590c9fe06d4313b7247470bcf15 | 953174dcb862a7a364efdb65e178dcd3aea5562e, 9f5315d3f4368590c9fe06d4313b7247470bcf15 |
| linux-kernel: Kernel | >=6.19.0 <7.3.2 | 7.3.2 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket