CVE-2026-99075: Linux kernel · rust_binder: reschedule node refcount update on thread exit
Affects Linux kernelSource GCVE Database
Not known to be exploited.
Data as of 28 Oct 2026, 01:31 UTC
Rated by Threat Radar · CVSS not yet scored by NVD
Exploitation evidence
Disclosed: evidence found.
CVE published 23 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Ubuntu 26.04 LTSlinuxpkg:deb/ubuntu/linux?arch=source&distro=resoluteOther threats | Affected
| Fixed in– |
Ubuntu 26.04 LTSlinux-awspkg:deb/ubuntu/linux-aws?arch=source&distro=resoluteOther threats | Affected
| Fixed in– |
Ubuntu 26.04 LTSlinux-azurepkg:deb/ubuntu/linux-azure?arch=source&distro=resoluteOther threats | Affected
| Fixed in– |
Ubuntu 26.04 LTSlinux-azure-fdepkg:deb/ubuntu/linux-azure-fde?arch=source&distro=resoluteOther threats | Affected
| Fixed in– |
Ubuntu 26.04 LTSlinux-gcppkg:deb/ubuntu/linux-gcp?arch=source&distro=resoluteOther threats | Affected
| Fixed in– |
Ubuntu 26.04 LTSlinux-gkepkg:deb/ubuntu/linux-gke?arch=source&distro=resoluteOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
A fix has been implemented that correctly reschedules the pending node refcount update on thread exit. Users should apply the updated Linux kernel versions that include this fix. No additional mitigation steps are indicated.
Description
A vulnerability in the Linux kernel's rust_binder component causes a node's delivery and count state to become desynchronized when a thread exits while holding a pending node refcount increment. This occurs because the refcount increment is dropped due to no-op cancel functions, potentially causing the node to never be freed from the process's nodes tree after all external references are dropped. The issue is fixed by rescheduling the pending refcount update to the process's work queue on thread exit.
References
- ubuntu.com/security/CVE-2026-99075 (opens in a new tab)
- cve.org/CVERecord?id=CVE-2026-99075 (opens in a new tab)
- git.kernel.org/stable/c/2a74ccd1bcc170e66525f34e9de8652b57e2cf3d (opens in a new tab)
- git.kernel.org/stable/c/71cbad138969edecef01b28dff87d91b56db538d (opens in a new tab)
- git.kernel.org/stable/c/fb0f8dfc5a030ed3d60a1d03acdc99c90ee99fc1 (opens in a new tab)