Local privilege escalation via Binder teardown race
Published Jul 25, 2026 · Updated Jul 25, 2026
Use-after-free in the Linux kernel Binder subsystem allows local users to corrupt kernel memory through Binder device ioctls. binder_thread_release() accesses a binder_transaction after t->to_proc is cleared while binder_free_transaction() can free it because t->to_proc is not read under the transaction lock. Low-privileged access to Binder or a private BinderFS device is sufficient, enabling kernel-memory disclosure, arbitrary writes, code execution, or a kernel panic.
Summary
What happened
Use-after-free in the Linux kernel Binder subsystem allows local users to corrupt kernel memory through Binder device ioctls. binder_thread_release() accesses a binder_transaction after t->to_proc is cleared while binder_free_transaction() can free it because t->to_proc is not read under the transaction lock. Low-privileged access to Binder or a private BinderFS device is sufficient, enabling kernel-memory disclosure, arbitrary writes, code execution, or a kernel panic.
The record
- CVE
- CVE-2026-64469
- Published
- Jul 25, 2026
- Updated
- Jul 25, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- T1068
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 25, 2026CVE publishedPublication date reported by the CVE source.
- Jul 25, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=4.14
- Affected versionversion=7a4408c6bd3eb1dafba67986259191be081e3efb <114a116aaa5f0295376cdf12da743c5bce3b20ce
- Affected versionversion=7a4408c6bd3eb1dafba67986259191be081e3efb <1f96f8c0a6ed4f6d01d3dd29ad0cbf08dde96082
- Affected versionversion=7a4408c6bd3eb1dafba67986259191be081e3efb <38e1a71728e5795b670cc159c18e286a40aeebb4
- Affected versionversion=7a4408c6bd3eb1dafba67986259191be081e3efb <df1a17abba8d6fac5f965adcb8113ceace6e4949
- Affected versionversion=7a4408c6bd3eb1dafba67986259191be081e3efb <e63032dc715026a96bcaa13d375a8e15c91caa84
- Affected versionversion=7a4408c6bd3eb1dafba67986259191be081e3efb <ea02df466df60ecd758eb3b4df3f0cadc5c886ce
- Affected versionversion=7a4408c6bd3eb1dafba67986259191be081e3efb <ef5439ba5b9ac93349f5df12ef88b42a0ce26340
- Affected versionversion=7a4408c6bd3eb1dafba67986259191be081e3efb <faa070c7ad8ba25dcd0b12d7cdbb419e336f5391
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo