Description
In the Linux kernel, the following vulnerability has been resolved: rust_binder: reschedule node refcount update on thread exit When a thread exits via BINDER_THREAD_EXIT, its pending work items are cancelled. If a thread exits while holding a pending node refcount increment (e.g. pushed as deferred work to that thread), the refcount increment was previously dropped because Node::cancel() and NodeWrapper::cancel() were no-ops. Dropping the refcount update leaves the node's delivery state and count state desynchronized, and userspace will not receive the notification, which can cause the node to never be freed from the process's nodes tree when all external references are dropped. Fix this by implementing DeliverToRead::cancel() for Node and NodeWrapper to move the pending refcount update to the process's work queue on thread exit so another thread can deliver it to userspace.
Affected products
Version statuses are supplied by the assigning organization. Consult the original record for detailed ranges and platform conditions.
Linux Linux
Default version status: unaffected
eafedbc7c050c44744fbdf80bdf3315e860b7513 to < 71cbad138969edecef01b28dff87d91b56db538daffectedeafedbc7c050c44744fbdf80bdf3315e860b7513 to < fb0f8dfc5a030ed3d60a1d03acdc99c90ee99fc1affectedeafedbc7c050c44744fbdf80bdf3315e860b7513 to < 2a74ccd1bcc170e66525f34e9de8652b57e2cf3daffected
Linux Linux
Default version status: affected
6.18affected0 to < 6.18unaffected6.18.57 to ≤ 6.18.*unaffected7.2.11 to ≤ 7.2.*unaffected7.3 to ≤ *unaffected