Loading vulnerability…
CVE-2022-20421 is a use-after-free vulnerability in the Android kernel Binder driver’s binder_inc_ref_for_node function. Improper lifetime handling can create a condition in which freed memory is accessed, enabling memory corruption and potential local elevation of privilege.
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.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos (1 hidden).
This repository contains a full exploit for CVE-2022-20421, a local privilege escalation vulnerability in the Android Binder driver. The exploit targets Android devices running kernel versions 5.4.x and 5.10.x with security patch levels before October 2022. The structure includes a native C exploit (src/exploit.c and related files), a Makefile for building a shared library (libbadspin.so), and an Android demo app (Java/Gradle project in the app/ directory) that loads the exploit via LD_PRELOAD. The exploit achieves kernel read/write primitives and, on Google Pixel 6, full root and SELinux bypass. Device-specific configurations are managed in src/dev_config.h. The exploit can be run from an adb shell or via the demo app. The repository also includes a bundled copy of libsepol for SELinux policy manipulation. Key endpoints include /dev/hwbinder (Binder device), /data/local/tmp/libbadspin.so (payload location), and /system/lib64/libc.so (used for file spraying). The code is mature and operational, with device adaptation possible via configuration changes.
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.
2 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
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.