Description
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 products
Version statuses are supplied by the assigning organization. Consult the original record for detailed ranges and platform conditions.
Linux Linux
Default version status: unaffected
dbb17c9ea7567c6ecefe47104cfcc255b91e4089 to < efb488fd08fd9993d5bad6b6e2848d12a16e1a3aaffecteddbb17c9ea7567c6ecefe47104cfcc255b91e4089 to < 985955d8e6b2b15cfd65b7ac6893e3a5a90c5870affected
Linux Linux
Default version status: affected
7.3affected0 to < 7.3unaffected7.3.2 to ≤ 7.3.*unaffected7.4-rc1 to ≤ *unaffected