binder: signal epoll threads of self-work
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
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.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- Linux Linux
Version range not reported
- Linux Linux
2.6.29
References 8
git.kernel.org
- stable/c/dd64bb8329ce0ea27bc557e4160c2688835402ac
- stable/c/42beab162dcee1e691ee4934292d51581c29df61
- stable/c/a423042052ec2bdbf1e552e621e6a768922363cc
- stable/c/82722b453dc2f967b172603e389ee7dc1b3137cc
- stable/c/90e09c016d72b91e76de25f71c7b93d94cc3c769
- stable/c/a7ae586f6f6024f490b8546c8c84670f96bb9b68
- stable/c/93b372c39c40cbf179e56621e6bc48240943af69
- stable/c/97830f3c3088638ff90b20dfba2eb4d487bf14d7