Loading vulnerability…
CVE-2025-68260 is a race condition in the Linux kernel's Rust Binder implementation affecting handling of a node's death_list. The flaw arises from an unsafe list removal operation on NodeDeath objects that assumes an element is either in its owner's list or in no list at all. In practice, Node::release acquires the lock, moves all list items to a temporary local list, releases the lock, and then iterates that local list. While this is happening, another thread can invoke the unsafe remove operation against the original list state, causing concurrent manipulation of the same prev/next list pointers without proper synchronization. This breaks list integrity and results in memory corruption in kernel space. The issue was fixed by changing Node::release to pop items directly from the original list rather than moving them to a separate local list for later processing.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
35 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A security vulnerability identified in the Rust implementation of the Android Binder driver (IPC subsystem), highlighted as an early notable CVE affecting Rust-based system code.
The first vulnerability in the Linux kernel's Rust codebase, identified as CVE-2025-68260.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.