rust_binder: reschedule node refcount update on thread exit
- 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
- Fix
- Fixed in 6.18.57, 7.2.11
- 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
Summary
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.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- Linux Linux
From eafedbc7c050c44744fbdf80bdf3315e860b7513 · fixed in 71cbad138969edecef01b28dff87d91b56db538d; From eafedbc7c050c44744fbdf80bdf3315e860b7513 · fixed in fb0f8dfc5a030ed3d60a1d03acdc99c90ee99fc1; From eafedbc7c050c44744fbdf80bdf3315e860b7513 · fixed in 2a74ccd1bcc170e66525f34e9de8652b57e2cf3d
- Linux Linux
6.18
- KernelLinux
From 6.18.0 · fixed in 6.18.57; From 6.19.0 · fixed in 7.2.11