CVE-2026-99075
rust_binder: reschedule node refcount update on thread exit
No known exploitation. No EPSS score yet. Fixed versions are out.
What to do
Find your product and version, then upgrade to the build on the right.
- LinuxAffected: ≥ eafedbc7c050c44744fbdf80bdf3315e860b7513, < 71cbad138969edecef01b28dff87d91b56db538dUpgrade to: 71cbad138969edecef01b28dff87d91b56db538dAffected: ≥ eafedbc7c050c44744fbdf80bdf3315e860b7513, < fb0f8dfc5a030ed3d60a1d03acdc99c90ee99fc1Upgrade to: fb0f8dfc5a030ed3d60a1d03acdc99c90ee99fc1Affected: ≥ eafedbc7c050c44744fbdf80bdf3315e860b7513, < 2a74ccd1bcc170e66525f34e9de8652b57e2cf3dUpgrade to: 2a74ccd1bcc170e66525f34e9de8652b57e2cf3dStated by: CVE record
Versions as the sources state them. Full version matrix after sign-in
What it is
From the CVE record
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.
In plain language
No plain-language summary for this CVE yet.
Exploitation
Where each signal puts this CVE on the scale from published to confirmed exploited.
- CISA KEV
Not in the catalog. CISA has not confirmed exploitation.
- Public exploits
No public exploit or proof of concept found in the sources we track.
- EPSS
No EPSS score yet. New CVEs are usually scored within a few days.
Lifecycle
2 events over 0 days, from the signal feeds we watch.
- Publishedrecord updated
Affected products
Sources
Watch the software you run.
My Stack ranks new CVEs for your products by real-world exploitation, so the next serious one reaches you without reading every advisory.
We'll flag the next CVE, public exploit or patch for Linux, not every advisory.
A free account adds
- The full version matrix and every affected product
- Exploit links, proofs of concept and Metasploit modules
- Email alerts for the products you watch
- The same data over REST API, MCP and CLI