{"resultsPerPage":1,"startIndex":0,"totalResults":1,"format":"NVD_CVE","version":"2.0","timestamp":"2026-04-17T20:30:08.797","vulnerabilities":[{"cve":{"id":"CVE-2025-40305","sourceIdentifier":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","published":"2025-12-08T01:16:02.700","lastModified":"2026-04-15T00:35:42.020","vulnStatus":"Deferred","cveTags":[],"descriptions":[{"lang":"en","value":"In the Linux kernel, the following vulnerability has been resolved:\n\n9p/trans_fd: p9_fd_request: kick rx thread if EPOLLIN\n\np9_read_work() doesn't set Rworksched and doesn't do schedule_work(m->rq)\nif list_empty(&m->req_list).\n\nHowever, if the pipe is full, we need to read more data and this used to\nwork prior to commit aaec5a95d59615 (\"pipe_read: don't wake up the writer\nif the pipe is still full\").\n\np9_read_work() does p9_fd_read() -> ... -> anon_pipe_read() which (before\nthe commit above) triggered the unnecessary wakeup. This wakeup calls\np9_pollwake() which kicks p9_poll_workfn() -> p9_poll_mux(), p9_poll_mux()\nwill notice EPOLLIN and schedule_work(&m->rq).\n\nThis no longer happens after the optimization above, change p9_fd_request()\nto use p9_poll_mux() instead of only checking for EPOLLOUT."}],"metrics":{},"references":[{"url":"https://git.kernel.org/stable/c/242531004d7de8c159f9bfadebe33fe8060b1046","source":"416baaa9-dc9f-4396-8d5f-8c081fb06d67"},{"url":"https://git.kernel.org/stable/c/e8fe3f07a357c39d429e02ca34f740692d88967a","source":"416baaa9-dc9f-4396-8d5f-8c081fb06d67"}]}}]}