# Android Binder C implementation removed from Linux kernel in favor of Rust

> **Key takeaway:** The Linux kernel has fully replaced the C implementation of Android's Binder IPC driver with its Rust equivalent, marking a significant milestone for Rust in kernel development.

**Published:** 2026-10-30T17:46:46+00:00 
**Source:** Linux Weekly News (LWN.net) 
**Category:** kernel-os 
**Canonical URL:** https://fosswire.org/news/android-binder-c-implementation-removed-from-linux-kernel-in.html 

## Summary
At Kangrejos 2026, Carlos Llamas announced the deletion of the C implementation of Android's Binder driver from the Linux kernel, completing a multi-year transition to a Rust-based replacement. Binder serves as the primary interprocess communication mechanism for Android devices, handling everything from service registration to cross-process method invocation. The removal was met with general applause from attendees and represents one of the most substantial Rust-in-kernel adoptions to reach completion.

Alice Ryhl, who has contributed to the Rust Binder implementation for several years, joined Llamas in discussing the technical challenges encountered during the rewrite. The transition required careful attention to maintaining compatibility with Android's extensive user-space dependencies while leveraging Rust's memory safety guarantees. The completed removal signals that the Rust implementation has achieved sufficient maturity and testing coverage to serve production Android workloads.

## What the Binder Rust transition involved
- **Driver scope:** Binder is Android's core IPC mechanism, used for service lookup, transaction handling, and cross-process object reference management across the entire Android stack.
- **Implementation history:** The Rust Binder rewrite has been under active development for multiple years, with Alice Ryhl as a key contributor working through gradual upstream integration.
- **Removal criteria:** The C code deletion indicates the Rust implementation has passed sufficient validation to handle production Android device workloads without fallback requirements.
- **Kernel Rust milestone:** This represents one of the largest and most visible subsystem transitions from C to Rust in the upstream kernel, beyond smaller driver experiments.
- **Compatibility requirements:** The rewrite had to maintain exact behavioral compatibility with Android's extensive user-space Binder ABI, including complex edge cases in transaction threading and reference counting.

## Why it matters
The Binder removal validates Rust as a viable language for rewriting core kernel subsystems with complex concurrency and security requirements, likely accelerating adoption for other driver rewrites. For Android vendors and custom ROM developers, this transition reduces the attack surface for memory safety vulnerabilities in a component that handles all privileged interprocess communication. Linux distributions shipping Android compatibility layers or containerized Android environments will eventually inherit these changes through stable kernel updates.