Unknown

CVE-2026-99075 — rust_binder: reschedule node refcount update on thread exit

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.

Published Oct 23, 2026 · Updated Oct 23, 2026 · Sources: CVE Program (cve.org) e CISA ADP, NIST National Vulnerability Database · CNA: Linux

Low

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

No exploitation signal in the sources consulted so far.

How the score was calculated

EPSS 0.2% (30-day exploitation probability)+1

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation

Not confirmed

Not in CISA KEV — an absence of record, not proof it is unexploited.

EPSS FIRST

0.19%

ahead of 9% of scored CVEs · Oct 30, 2026

Affects

Linux

CVSS base

—

Score not published yet.

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

Identify exposed assets running the affected vendor/product/version combinations (Linux Linux).
No fix documented in the sources: reduce exposure and monitor the vendor advisory.
Search available logs for exploit probes, errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

Vendor	Product	Versions	Status	Source
Linux	Linux	≥ eafedbc7c050c44744fbdf80bdf3315e860b7513 and < 71cbad138969edecef01b28dff87d91b56db538d≥ eafedbc7c050c44744fbdf80bdf3315e860b7513 and < fb0f8dfc5a030ed3d60a1d03acdc99c90ee99fc1≥ eafedbc7c050c44744fbdf80bdf3315e860b7513 and < 2a74ccd1bcc170e66525f34e9de8652b57e2cf3dversion 6.18	Vulnerable	CVE Program (cve.org) e CISA ADP

EPSS over time FIRST

Oct 24, 2026 → Oct 30, 2026 · 7 reading(s) · max 0.21%

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

Not enough vector or weakness data: use the affected application’s logs as a starting point.

application logs

Timeline

What happened to this CVE, newest first.

2026
Source status changed · Published → Received
Oct 23, 2026 · NIST National Vulnerability Database
Record published
Oct 23, 2026
Source status changed · → Published
Oct 23, 2026 · CVE Program (cve.org) e CISA ADP
Record created in this database
Oct 23, 2026 · CVE Program (cve.org) e CISA ADP
CVE published
Oct 23, 2026 · Linux

Source activity

Repeated readings are counted rather than listed.

1× Official description updated · Oct 23, 2026 – Oct 23, 2026

References

3 on the record

git.kernel.org/stable/c/2a74ccd1bcc170e66525f34e9de8652b57e2cf3d
CVE Program (cve.org) e CISA ADP
git.kernel.org/stable/c/fb0f8dfc5a030ed3d60a1d03acdc99c90ee99fc1
CVE Program (cve.org) e CISA ADP
git.kernel.org/stable/c/71cbad138969edecef01b28dff87d91b56db538d
CVE Program (cve.org) e CISA ADP

Elsewhere on this site

Linux
every CVE for this vendor

Related CVEs (same products)

Unknown CVE-2026-99216 Drivers: hv: Don't reset VMBus connection state on error/exit paths 2d
Unknown CVE-2026-99215 power: supply: core: prevent unregistering a power supply while a callback runs 2d
Unknown CVE-2026-99207 scsi: target: Disable interrupts while holding delayed_cmd_lock 2d
Unknown CVE-2026-99208 drm/xe/oa: Zero OA buffer at allocation 2d
Unknown CVE-2026-99209 drm/xe: skip eviction of a BO with no resource 2d
Unknown CVE-2026-99210 accel/rocket: clear rdev on device init failure 2d

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

No CVSS score published by NVD, the CNA, CISA or GitHub so far.
No fixed version, patch or mitigation documented.
No CISA SSVC assessment.
No CWE classification.
No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2026-99075 is "rust_binder: reschedule node refcount update on thread exit", rated Unknown. It affects Linux (Linux); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. EPSS 0.19% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.