Answer in brief
CVE-2026-99075 records a Unknown severity vulnerability in rust_binder: reschedule node refcount update on thread exit. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=eafedbc7c050c44744fbdf80bdf3315e860b7513 <71cbad138969edecef01b28dff87d91b56db538d || >=eafedbc7c050c44744fbdf80bdf3315e860b7513 <fb0f8dfc5a030ed3d60a1d03acdc99c90ee99fc1 || >=eafedbc7c050c44744fbdf80bdf3315e860b7513 <2a74ccd1bcc170e66525f34e9de8652b57e2cf3d | 71cbad138969edecef01b28dff87d91b56db538d, fb0f8dfc5a030ed3d60a1d03acdc99c90ee99fc1, 2a74ccd1bcc170e66525f34e9de8652b57e2cf3d |
| Linux/Linuxgeneric | 6.18 | Not reported |
Published upstream
Oct 23, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Oct 23, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Oct 23, 2026
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.
Quoted source text, attributed separately from HOL analysis.