Bug 2576747 (CVE-2026-99321) - CVE-2026-99321 kernel: kernel: delayed event notifications via unhandled epoll wakeups in Rust Binder
Summary: CVE-2026-99321 kernel: kernel: delayed event notifications via unhandled epol...
Keywords:
Status: NEW
Alias: CVE-2026-99321
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Product Security DevOps Team
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-11-19 14:39 UTC by OSIDB Bzimport
Modified: 2026-11-19 18:57 UTC (History)
17 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

Description OSIDB Bzimport 2026-11-19 14:39:40 UTC
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.


Note You need to log in before you can comment on or make changes to this bug.