CVE-2026-64469: Linux Kernel use-after-free in binder_thread_release

CVE-2026-64469 · Severity: info · CVSS 7.8 · Published 2026-07-25

A vulnerability was discovered in the Android Binder component of the Linux kernel, which manages communication between different processes. A race condition occurs when a thread exits while another process is simultaneously cleaning up data, potentially allowing an attacker to crash the system or execute unauthorized code. This issue primarily affects Android-based systems or Linux distributions using the Binder driver.

Technologies: Linux Kernel. Vendors: Linux.

Quick answers

Is CVE-2026-64469 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-64469 being exploited in the wild.
How severe is CVE-2026-64469?
Informational severity, with a CVSS score of 7.8, published 25 July 2026.
Which products and versions are affected?
Linux Kernel 7.1-rc5.
Is there a fix for CVE-2026-64469?
A patch was published on 2026-07-03: Patch committed to stable kernel tree Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-64469 attacked?
It is attacked with local access, in an operating system.
Am I affected by CVE-2026-64469?
Check whether you run Linux Kernel at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

A use-after-free (UAF) vulnerability exists in the binder_thread_release() function of the Android Binder driver (drivers/android/binder.c). The root cause is a race condition where binder_thread_release() attempts to access a transaction object that is being concurrently freed by binder_free_transaction() during process termination. Specifically, if a transaction has no associated 'to_proc', the 'inner_lock' is not acquired, allowing binder_free_transaction() to kfree the transaction while binder_thread_release() is still walking the transaction stack. An attacker with local access could exploit this race to achieve arbitrary memory writes or a kernel panic. The fix involves ensuring that binder_free_transaction() reads the 'to_proc' pointer under the transaction spinlock to serialize access.

Affected products

  • Linux Linux Kernel 7.1-rc5

Timeline

  • 2026-06-19: disclosed: Initial patch submitted by Google engineers
  • 2026-07-03: patched: Patch committed to stable kernel tree
  • 2026-07-25: advisory: CVE-2026-64469 published

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.