cve.bz

CVE-2019-2215 (Bad Binder) Android Kernel Use-After-Free Vulnerability

7.8 highKEVExploitEPSS 72%Fix available

Known as Bad Binder

High (7.8) in Android Android Kernel. In CISA KEV since 2021-11-03. EPSS 72% estimated probability of exploitation activity in the next 30 days.

On this page
A use-after-free in binder.c allows an elevation of privilege from an application to the Linux Kernel. No user interaction is required to exploit this vulnerability, however exploitation does require either the installation of a malicious local application or a separate vulnerability in a network facing application.Product: AndroidAndroid ID: A-141720095

Severity

CVSS 3.1

7.8 high
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS
72% (unchanged from 72% a week ago; 72% 30 days ago) estimated probability of exploitation activity in the next 30 days; 99th percentile. Scored 2026-11-21. A forecast for this CVE across the internet, not for your own systems.
CISA KEV
listed 2021-11-03, due 2022-05-03
CISA's assessment (SSVC)
Exploitation: active · Automatable: no · Technical impact: total, assessed 2025-02-07. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-416 Use After Free
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2019-2215 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2019-2215?via=ask-ai-copy and https://cve.bz/cve/CVE-2019-2215?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2019-2215 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
debian:debian_linux8.0
canonical:ubuntu_linux16.04
huawei:alp-al00b_firmwarebefore 10.0.0.162\(c00e156r2p4\)
huawei:alp-tl00b_firmwarebefore 10.0.0.162\(c01e156r1p4\)
huawei:anne-al00_firmwarebefore 9.1.0.126\(c00e126r1p7t8\)
huawei:ares-al00b_firmwarebefore 9.1.0.165\(c00e165r2p5t8\)
huawei:ares-al10d_firmwarebefore 9.1.0.165\(c00e165r2p5t8\)
huawei:ares-tl00chw_firmwarebefore 8.2.0.163\(c01r2p1\)
huawei:bla-al00b_firmwarebefore 10.0.0.170\(c786e170r2p4\)
huawei:bla-l29c_firmwarebefore 9.1.0.300\(c432e4r1p11t8\)
huawei:bla-tl00b_firmwarebefore 10.0.0.170\(c01e170r1p4\)
huawei:barca-al00_firmwarebefore 8.0.0.377\(c00\)
huawei:berkeley-l09_firmwarebefore 9.1.0.351\(c432e5r1p13t8\)
huawei:berkeley-tl10_firmwarebefore 9.1.0.333\(c01e333r1p1t8\)
huawei:columbia-al00a_firmwarebefore 8.1.0.186\(c00gt\)
huawei:columbia-l29d_firmwarebefore 9.1.0.325\(c432e4r1p12t8\)
huawei:cornell-tl10b_firmwarebefore 9.1.0.321\(c01e320r1p1t8\)
huawei:duke-l09i_firmwarebefore 9.0.1.171\(c675e6r1p5t8\)
huawei:dura-al00a_firmwarebefore 1.0.0.190\(c00\)
huawei:figo-al00a_firmwarebefore 9.1.0.130\(c00e115r2p8t8\)
huawei:florida-al20b_firmwarebefore 9.1.0.128\(c00e112r1p6t8\)
huawei:florida-l03_firmwarebefore 9.1.0.154\(c605e7r1p2t8\)
huawei:florida-l21_firmwarebefore 9.1.0.154\(c605e7r1p2t8\)
huawei:florida-l22_firmwarebefore 9.1.0.150\(c636e6r1p5t8\)
huawei:florida-tl10b_firmwarebefore 9.1.0.128\(c01e112r1p6t8\)
huawei:mate_rs_firmware9.1.0.321(c786e320r1p1t8)
huawei:p20_firmwarebefore 9.1.0.312\(c00e312r1p1t8\)
huawei:p20_lite_firmwarebefore 9.1.0.200\(c605e4r1p3t8\)
huawei:p20_lite_firmwarebefore 9.1.0.200\(c635e5r1p1t8\)
huawei:p20_lite_firmwarebefore 9.1.0.246\(c432e6r1p7t8\)
huawei:y9_2019_firmwarebefore 9.1.0.297\(c605e4r1p1t8\)
huawei:nova_2s_firmwarebefore 9.1.0.210\(c01e110r1p9t8\)
huawei:nova_3_firmwarebefore 9.1.0.351\(c00e351r1p1t8\)
huawei:nova_3e_firmwarebefore 9.1.0.200\(c636e4r1p5t8\)
huawei:p20_lite_firmwarebefore 9.1.0.200\(c636e4r1p5t8\)
huawei:p20_lite_firmwarebefore 9.1.0.201\(c636e4r1p5t8\)
huawei:nova_3e_firmwarebefore 9.1.0.201\(c636e4r1p5t8\)
huawei:nova_3e_firmwarebefore 9.1.0.201\(zafc185e4r1p8t8\)
huawei:p20_lite_firmwarebefore 9.1.0.201\(zafc185e4r1p8t8\)
huawei:honor_view_20_firmwarebefore 10.1.0.214\(c10e5r4p3\)
huawei:jakarta-al00a_firmwarebefore 9.1.0.260\(c00e120r2p2\)
huawei:johnson-tl00d_firmwarebefore 9.1.0.219\(c01e18r3p2t8\)
huawei:leland-al10b_firmwarebefore 9.1.0.130\(c00e112r2p10t8\)
huawei:leland-l21a_firmwarebefore 9.1.0.156\(c185e5r1p5t8\)
huawei:leland-l32a_firmwarebefore 9.1.0.153\(c675e6r1p4t8\)
huawei:leland-tl10b_firmwarebefore 9.1.0.130\(c01e112r2p10t8\)
huawei:leland-tl10c_firmwarebefore 9.1.0.130\(c01e112r2p10t8\)
huawei:lelandp-al00c_firmwarebefore 9.1.0.130\(c00e112r2p10t8\)
huawei:lelandp-l22c_firmwarebefore 9.1.0.156\(c636e5r1p5t8\)
huawei:neo-al00d_firmwarebefore 9.1.0.321\(c786e320r1p1t8\)
huawei:princeton-al10b_firmwarebefore 10.1.0.160\(c00e160r2p11\)
huawei:rhone-al00_firmwarebefore 8.0.0.376\(c00\)
huawei:stanford-l09_firmwarebefore 9.1.0.211\(c635e2r1p4t8\)
huawei:stanford-l09s_firmwarebefore 9.1.0.210\(c432e2r1p5t8\)
huawei:sydney-al00_firmwarebefore 9.1.0.212\(c00e62r1p7t8\)
huawei:sydney-tl00_firmwarebefore 9.1.0.212\(c01e62r1p7t8\)
huawei:sydneym-al00_firmwarebefore 9.1.0.212\(c00e62r1p7t8\)
huawei:tony-al00b_firmwarebefore 10.0.0.175\(c00e59r2p11\)
huawei:tony-tl00b_firmwarebefore 10.0.0.175\(c01e59r2p11\)
huawei:yale-al00a_firmwarebefore 10.1.0.160\(c00e160r8p12\)
huawei:yale-l21a_firmwarebefore 10.1.0.231\(c10e3r3p2\)
huawei:yale-tl00b_firmwarebefore 10.1.0.160\(c01e160r8p12\)
huawei:honor_9i_firmwarebefore 9.1.0.130\(c00e112r2p10t8\)

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian8linux3.16.81-1DLA-2068-1
Debian8linux-4.94.9.210-1~deb8u1DLA-2114-1
Debian12, 13, 14linux4.15.4-1DEBIAN-CVE-2019-2215
Ubuntu16.04:LTSlinux4.4.0-168.197UBUNTU-CVE-2019-2215 USN-4186-1
Ubuntu16.04:LTSlinux-aws4.4.0-1098.109UBUNTU-CVE-2019-2215 USN-4186-1
Ubuntu16.04:LTSlinux-azure4.15.0-1013.13~16.04.2UBUNTU-CVE-2019-2215
Ubuntu16.04:LTSlinux-gcp4.15.0-1014.14~16.04.1UBUNTU-CVE-2019-2215
Ubuntu16.04:LTSlinux-hwe4.15.0-24.26~16.04.1UBUNTU-CVE-2019-2215
Ubuntu16.04:LTSlinux-hwe-edgeno fix listedUBUNTU-CVE-2019-2215
Ubuntu16.04:LTSlinux-kvm4.4.0-1062.69UBUNTU-CVE-2019-2215 USN-4186-1
Ubuntu16.04:LTSlinux-raspi24.4.0-1125.134UBUNTU-CVE-2019-2215
Ubuntu16.04:LTSlinux-snapdragon4.4.0-1129.137UBUNTU-CVE-2019-2215
Ubuntu18.04:LTSlinux-snapdragon4.15.0-1053.57UBUNTU-CVE-2019-2215
Ubuntu20.04:LTSlinux-gke, linux-riscv, linux-azure-fdeno fix listedUBUNTU-CVE-2019-2215
Ubuntu22.04:LTSlinux-riscv, linux-realtime, linux-intel-iot-realtimeno fix listedUBUNTU-CVE-2019-2215
4 more for Ubuntu in the JSON and on Ubuntu's page.

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu.

Red Hat

Red Hat rates this Moderate.

Red Hat's mitigation

There is no mitigation required for this flaw as it does not affect shipping Red Hat Enterprise Linux kernels.

ProductPackageStateAdvisory
Red Hat Enterprise Linux 5kernelNot affected
Red Hat Enterprise Linux 6kernelNot affected
Red Hat Enterprise Linux 7kernelNot affected
Red Hat Enterprise Linux 7kernel-altNot affected
Red Hat Enterprise Linux 7kernel-rtNot affected
Red Hat Enterprise Linux 8kernelNot affected
Red Hat Enterprise Linux 8kernel-rtNot affected
Red Hat Enterprise MRG 2kernel-rtNot affected

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2019-2215.

Public exploits

GitHub PoC

Repositories on GitHub named after this CVE or listed for it by the PoC-in-GitHub index. For those marked Harbor Check: matches CVE, Flawharbor read the code and found it implements this CVE's exploitation technique: read, not run, and its dependencies only checked for warning signs, so a pointer and no guarantee. The rest are unverified: some hold a working proof of concept, some nothing useful, and some malware made to look like one. Read the code before you run any of it. How Harbor Check reads them, and what it found.

  • 0xbinder/CVE_2019_2215 Harbor Check: matches CVE 6 stars, C, created
    A rewritten Proof-of-Concept / Local Privilege Escalation (LPE) exploit targeting CVE-2019-2215, a Use-After-Free vulnerability in the Andr…
  • wired0ut/CVE-2019-2215 Harbor Check: matches CVE 4 stars, C, created
    Full exploit for the Android vulnerability Bad Binder found in early Google Pixel phones.
  • Begitdj/cve-2019-2215-markw Harbor Check: matches CVE 1 star, C, created
  • WJNKAC/CVE-2019-2215-vivo-Y66i Harbor Check: matches CVE 0 stars, C, created
    在AI辅助下完成的 vivo Y66i 提权路径
  • RxinnotRstar/CVE-2019-2215-ForMIpad4 Harbor Check: matches CVE 0 stars, Java, created
    使用CVE-2019-2215 对miui10的小米平板4的临时root获取软件。
4 more

References

Check your stackJSON