New Linux Kernel Rust Vulnerability Triggers System Crashes

A critical vulnerability has been discovered in the Linux kernel’s Rust Binder module, which can cause system crashes and memory corruption due to a race condition.

The issue has been assigned CVE-2025-68260 and affects the kernel’s inter-process communication mechanism, requiring immediate attention from system administrators and kernel maintainers.

The Vulnerability

The vulnerability exists in the Rust Binder component’s death_list handling mechanism, specifically in the Node::release function, where an unsafe operation removes items from a linked list without proper synchronization.

The problematic code attempts to manipulate list pointers without ensuring exclusive access, creating a dangerous race condition that can lead to memory corruption.

The issue arises from a specific implementation pattern that involves acquiring a lock, moving list items to a local stack-based list, and then releasing the lock before iterating through the items, creating a window of opportunity for concurrent access to the prev/next pointers.

When this race condition is triggered, systems experience kernel panics and page faults, resulting in errors such as “Unable to handle kernel paging request at virtual address.”

The vulnerability manifests as internal memory corruption, resulting in kernel oops messages and system instability, and can cause devices to crash with unexpected reboots and service interruptions.

The vulnerability was introduced in kernel version 6.18 with a specific commit change to the binder code and affects the drivers/android/binder/node.rs file directly.

The issue has been patched in kernel 6.18.1 and 6.19-rc1, with fixes available in the upstream kernel repositories.

The Linux kernel development team strongly recommends updating to the latest stable kernel version to maintain system stability and prevent unexpected downtime.

While full kernel updates are preferred, users unable to update immediately can apply specific commits from the kernel repositories to resolve this race condition.

System administrators should prioritize patching this vulnerability to prevent system crashes, memory corruption, and unexpected downtime.