binder: signal epoll threads of self-work
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 457b9a6f09f011ebcb9b52cc203a6331a6fc2de7 · < a7ae586f6f6024f490b8546c8c84670f96bb9b68| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
binder: signal epoll threads of self-work
In (e)poll mode, threads often depend on I/O events to determine when data is ready for consumption. Within binder, a thread may initiate a command via BINDER_WRITE_READ without a read buffer and then make use of epoll_wait() or similar to consume any responses afterwards.
It is then crucial that epoll threads are signaled via wakeup when they queue their own work. Otherwise, they risk waiting indefinitely for an event leaving their work unhandled. What is worse, subsequent commands won't trigger a wakeup either as the thread has pending work.
From the CVE record · Linux
In the Linux kernel’s binder component, a thread using (e)poll can queue its own work without receiving a wakeup. It may then wait indefinitely, leaving that work unhandled; the input does not specify attacker access or user-interaction requirements.
Teams running the Linux kernel should check their systems; affected versions are not specified.