rust_binder: wake epoll on self-work queued to poll thread
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 985955d8e6b2b15cfd65b7ac6893e3a5a90c5870, Kernel efb488fd08fd9993d5bad6b6e2848d12a16e1a3a and Kernel 7.3.2.
In the Linux kernel, the following vulnerability has been resolved: rust_binder: wake epoll on self-work queued to poll thread When a thread pushes work to its own todo list, InnerThread::push_work() returns PushWorkRes::OkNotifyPoll if the thread uses epoll, but four call sites in thread.rs discard this return value. As a result, a non-blocking BC_* write that enqueues work onto the calling thread's todo list without also reading will not wake epoll. Check the return value and call self.process.notify_poll(false) when PushWorkRes::OkNotifyPoll is returned. This is similar to commit 97830f3c3088 ("binder: signal epoll threads of self-work"), but in C Binder pending thread work also prevented subsequent process work from waking epoll, causing a permanent hang, which is not the case in Rust Binder. This means that in practice, it merely delays notifications rather than completely failing to send them.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | =7.3, >=dbb17c9ea7567c6ecefe47104cfcc255b91e4089 <985955d8e6b2b15cfd65b7ac6893e3a5a90c5870, >=dbb17c9ea7567c6ecefe47104cfcc255b91e4089 <efb488fd08fd9993d5bad6b6e2848d12a16e1a3a | 985955d8e6b2b15cfd65b7ac6893e3a5a90c5870, efb488fd08fd9993d5bad6b6e2848d12a16e1a3a |
| linux-kernel: Kernel | >=7.3.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