CVE-2019-2215: Bad Binder
- Vendors
- NetAppHuawei TechnologiesGoogleDebian ProjectCanonical
CVE-2019-2215, also known as Bad Binder, is a use-after-free vulnerability in the Android Linux kernel's Binder inter-process communication driver. After BINDER_THREAD_EXIT invokes binder_thread_release(), epoll can retain a reference to a wait queue embedded in the freed binder_thread structure. Subsequent wait-queue removal accesses freed memory. Reclaiming that memory with attacker-controlled allocations enables kernel memory disclosure and corruption, potentially yielding arbitrary kernel read/write access and full device compromise from an unprivileged application. The vulnerability was exploited in the wild.
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.
Successful exploitation allows a local unprivileged process to compromise kernel memory and escalate to root. Demonstrated exploits modify process credentials and capabilities, disable SELinux enforcement and seccomp restrictions, and escape application confinement. This enables access to other applications' sensitive data, covert payload installation, and extensive device surveillance. Exploitation can also cause kernel crashes and local denial of service.
Mitigation
If you can’t patch tonight, do this now.
Restrict installation and execution of untrusted applications to reduce the local exploitation route, but do not rely on app-store distribution alone: malicious applications exploiting this vulnerability reached Google Play. Keep browsers and other network-facing applications updated to reduce opportunities to chain remote code execution with this kernel flaw. CONFIG_DEBUG_LIST blocks the documented Project Zero exploitation technique through list-integrity checks, but is not a substitute for patching. On suitably supported systems, kernel memory tagging can impede the underlying use-after-free exploitation, subject to allocation coverage and enforcement.
Remediation
Patch, then assume compromise.
Install device-manufacturer firmware or kernel updates containing the CVE-2019-2215 Binder lifetime-management fix, addressed in the October 2019 Android Security Bulletin. The underlying fix had reached upstream Linux and Android kernel branches in February 2018 but was absent from many shipped devices; verify its inclusion in the actual device build rather than relying solely on the Android major version. Replace unsupported devices that cannot receive a corrected kernel.
Exploits
32 exploits validated by Mallory's analysis. Hidden: 4 rejected by Mallory's analysis as not a working exploit; 2 not yet analyzed, such as Exploit-DB entries. Showing the 25 most capable, earliest first.
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.
References
Frequently asked questions
- Is CVE-2019-2215 exploited in the wild?
- Yes. As of Oct 30, 2026, Mallory has reports of exploitation in the wild, and CISA added it to KEV on Nov 3, 2021.
- Is there a public exploit for CVE-2019-2215?
- Yes. Mallory tracks 32 public exploits or proofs of concept for CVE-2019-2215, the earliest disclosed Sep 26, 2019.
- Is there a patch for CVE-2019-2215?
- Install device-manufacturer firmware or kernel updates containing the CVE-2019-2215 Binder lifetime-management fix, addressed in the October 2019 Android Security Bulletin. The underlying fix had reached upstream Linux and Android kernel branches in February 2018 but was absent from many shipped devices; verify its inclusion in the actual device build rather than relying solely on the Android major version.
- What products are affected by CVE-2019-2215?
- Google Android, NetApp A220 Firmware, NetApp A320 Firmware, NetApp A800 Firmware, NetApp Aff Baseboard Management Controller Firmware, and at least 72 more.
- How severe is CVE-2019-2215?
- CVE-2019-2215 has a CVSS v3.1 score of 7.8 (High) and an EPSS score of 72.1% (99th percentile) as of Oct 30, 2026.
Recent activity
16 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.