9p/trans_fd: p9_fd_request: kick rx thread if EPOLLIN
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 242531004d7de8c159f9bfadebe33fe8060b1046 and Kernel e8fe3f07a357c39d429e02ca34f740692d88967a.
In the Linux kernel, the following vulnerability has been resolved: 9p/trans_fd: p9_fd_request: kick rx thread if EPOLLIN p9_read_work() doesn't set Rworksched and doesn't do schedule_work(m->rq) if list_empty(&m->req_list). However, if the pipe is full, we need to read more data and this used to work prior to commit aaec5a95d59615 ("pipe_read: don't wake up the writer if the pipe is still full"). p9_read_work() does p9_fd_read() -> ... -> anon_pipe_read() which (before the commit above) triggered the unnecessary wakeup. This wakeup calls p9_pollwake() which kicks p9_poll_workfn() -> p9_poll_mux(), p9_poll_mux() will notice EPOLLIN and schedule_work(&m->rq). This no longer happens after the optimization above, change p9_fd_request() to use p9_poll_mux() instead of only checking for EPOLLOUT.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | =6.14, >=aaec5a95d59615523db03dd53c2052f0a87beea7 <242531004d7de8c159f9bfadebe33fe8060b1046, >=aaec5a95d59615523db03dd53c2052f0a87beea7 <e8fe3f07a357c39d429e02ca34f740692d88967a | 242531004d7de8c159f9bfadebe33fe8060b1046, e8fe3f07a357c39d429e02ca34f740692d88967a |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket