VulnerabilityPublished 23 Oct 2026

CVE-2026-99075: Linux kernel · rust_binder: reschedule node refcount update on thread exit

Affects Linux kernelSource CVE Database V5

Not known to be exploited · fixed in fb0f8dfc5a030ed3d60a1d03acdc99c90ee99fc1 : update Linux kernel when convenient.

Data as of 26 Oct 2026, 12:55 UTC

Severity

Unrated

Rated by Threat Radar · CVSS not yet scored by NVD

EPSS: 0.1% chance of exploitation in 30 days – higher than 8% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in fb0f8dfc5a030ed3d60a1d03acdc99c90ee99fc1, 71cbad138969edecef01b28dff87d91b56db538d, 2a74ccd1bcc170e66525f34e9de8652b57e2cf3d

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.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade Linux kernel to fb0f8dfc5a030ed3d60a1d03acdc99c90ee99fc1, 71cbad138969edecef01b28dff87d91b56db538d or 2a74ccd1bcc170e66525f34e9de8652b57e2cf3d.

Affected software

Product	Affected	Fixed in
LinuxLinux	Affected ≥ eafedbc7c050c44744fbdf80bdf3315e860b7513, < fb0f8dfc5a030ed3d60a1d03acdc99c90ee99fc1	Fixed in fb0f8dfc5a030ed3d60a1d03acdc99c90ee99fc1
LinuxLinux	Affected ≥ eafedbc7c050c44744fbdf80bdf3315e860b7513, < 71cbad138969edecef01b28dff87d91b56db538d	Fixed in 71cbad138969edecef01b28dff87d91b56db538d
LinuxLinux	Affected ≥ eafedbc7c050c44744fbdf80bdf3315e860b7513, < 2a74ccd1bcc170e66525f34e9de8652b57e2cf3d	Fixed in 2a74ccd1bcc170e66525f34e9de8652b57e2cf3d
LinuxLinux	Affected =6.18	Fixed in–

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.

References

Community reviews

Loading reviews…