# CVE-2026-64466: rust_binder: clear freeze listener on node removal

> A local attacker can trigger a memory leak in the Linux kernel binder driver by removing a node without clearing its freeze listener, potentially causing denial of service.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 25 Jul 2026
- **Updated:** 17 Aug 2026
- **Also known as:** BELL-CVE-2026-64466, DEBIAN-CVE-2026-64466, GHSA-5qhr-mh6g-f94h, ROOT-OS-UBUNTU-2204-CVE-2026-64466, UBUNTU-CVE-2026-64466

## What is CVE-2026-64466?

CVE-2026-64466 is a memory corruption vulnerability in Linux, published on 25 Jul 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

In the Linux kernel, the following vulnerability has been resolved:

rust_binder: clear freeze listener on node removal

Generally userspace is supposed to explicitly clear freeze listeners
before they drop the refcount on the node ref to zero, but there's
nothing forcing that. Currently, in this scenario the freeze listener
remains in the freeze_listeners rbtree and in the remote node's freeze
listener list, even though the ref for which the listener is registered
is gone. This could potentially lead to a memory leak due to a refcount
cycle. Thus, remove the freeze listener in this scenario.

## Which versions are affected by CVE-2026-64466?


## How do I fix CVE-2026-64466?

Apply the vendor's patch.

## Is CVE-2026-64466 being exploited?

There is no known exploitation of CVE-2026-64466 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-64466 and fix it if it is affected.

What it is: CVE-2026-64466 is a memory corruption vulnerability in Linux, published on 25 Jul 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-64466 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-64466/ (Markdown: https://insights.sbomify.com/CVE-2026-64466/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-64466
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-64466
- OSV: https://osv.dev/vulnerability/CVE-2026-64466

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-64466/
Summaries are generated and may contain mistakes; the official description above is the record.