CVE-2025-68260: Race condition in Linux kernel Rust Binder death-list handling
- Vendor
- Linux
CVE-2025-68260 is a race condition in the Linux kernel's Rust-based Android Binder driver. Node::release moves death-notification entries from a node's death_list into a temporary local list while holding the node lock, then releases the lock before iterating that list. Concurrent removal of a NodeDeath entry through the original death_list can modify the same entry's previous and next pointers without synchronization with the temporary list. This violates the safety assumptions of the unsafe list-removal operation, causing list-pointer corruption and kernel crashes.
Impact, mitigation & remediation
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
Concurrent death-list operations can corrupt kernel linked-list pointers, causing invalid memory accesses and kernel crashes that disrupt system availability. Arbitrary code execution, privilege escalation, and information disclosure are not established.
Mitigation
If you can’t patch tonight, do this now.
If immediate patching is not possible, reduce exposure by disabling or avoiding affected rust_binder functionality where operationally feasible, and limit access to Binder-related attack surfaces to trusted workloads only. Because this is a kernel race condition in core list handling, mitigation short of applying the fix is inherently limited.
Remediation
Patch, then assume compromise.
Apply the upstream Linux kernel fix for CVE-2025-68260 or a vendor kernel update incorporating it. The fix changes Node::release to pop entries directly from the original death_list rather than transferring them into a temporary list processed outside the original synchronization. Specific fixed kernel versions are not available.
Exploits
No public exploits tracked yet. Mallory keeps watching.
Affected products & vendors
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Frequently asked questions
- Is CVE-2025-68260 exploited in the wild?
- As of Nov 12, 2026, Mallory has no reports of CVE-2025-68260 being exploited in the wild. It is not listed in CISA KEV.
- Is there a public exploit for CVE-2025-68260?
- As of Nov 12, 2026, Mallory has found no public exploit for CVE-2025-68260.
- Is there a patch for CVE-2025-68260?
- Apply the upstream Linux kernel fix for CVE-2025-68260 or a vendor kernel update incorporating it. The fix changes Node::release to pop entries directly from the original death_list rather than transferring them into a temporary list processed outside the original synchronization.
- What products are affected by CVE-2025-68260?
- Linux Kernel.
- How severe is CVE-2025-68260?
- CVE-2025-68260 has a CVSS v3.1 score of 7.8 (High) and an EPSS score of 0.22% (13th percentile) as of Nov 12, 2026.
Recent activity
36 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.