CVE-2019-2215

CRITICALNVD 7.89.0▲
EchelonGraph scoreHIGH confidence

Score elevated to 9.0 because this CVE is listed on the CISA Known Exploited Vulnerabilities catalog (added 2021-11-03), indicating real-world exploitation has been confirmed by US federal agencies. NVD baseline CVSS 7.8 retained for reference. Confidence: HIGH.

Triggered by: CISA KEV (actively exploited)
Sources: cisa_kev, epss, ghsa, nvd
Trending — 4 sources updated this weekExploited in the wild
9.0EG
EchelonGraph verdictPatch nowTreat as an emergency — this is being exploited.
  • Actively exploited in the wild (CISA-KEV)
CISA-KEV: ExploitedEPSS PROB: 72%CVSS: 7.8Exploit: cisa kev · ssvc active · Metasploit · Exploit-DB (verified) · epss top5pct · epss high · public exploitExposed services: Not assessed

A fix is available — apply it.

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

CVSS v3
7.8
EG Score
9.0CRITICALhigh confidence
EG Risk
81
EG Risk 81/100CISA SSVC

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity90% × 45%
Exploitation100% × 40%
Automatability0% × 15%
CISA SSVC: Track at low, Attend at medium and Act at high mission impact.
Action: A fix is available. Apply it within your standard update timelines at low, sooner than that at medium and as soon as possible at high mission impact.
EPSS PROB
72%
EPSS %ILE
99th
KEV
⚠ Exploited

CISA SSVCTrack at low, Attend at medium and Act at high mission impact.

A fix is available. Apply it within your standard update timelines at low, sooner than that at medium and as soon as possible at high mission impact.

Exploitation active (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

October 11, 2019

Last Modified

October 24, 2025

Advisory Details (9)

Auto-updated Jun 3, 2026
Patch available.
generic

Android Security Bulletin—October 2019  |  Android Open Source Project

https://source.android.com/security/bulletin/2019-10-01
generic

NetApp Product Security

https://security.netapp.com/advisory/ntap-20191031-0005/
generic

Bugtraq: [slackware-security] Slackware 14.2 kernel (SSA:2019-311-01)

https://seclists.org/bugtraq/2019/Nov/11
genericMentions a patch (unverified)

[SECURITY] [DLA 2114-1] linux-4.9 security update

https://lists.debian.org/debian-lts-announce/2020/03/msg00001.html
genericMentions a patch (unverified)

[SECURITY] [DLA 2068-1] linux security update

https://lists.debian.org/debian-lts-announce/2020/01/msg00013.html
generic

Security Advisory - Use-after-free Vulnerability in Android Kernel

http://www.huawei.com/en/psirt/security-advisories/huawei-sa-20191030-01-binder-en
generic

Full Disclosure: CVE 2019-2215 Android Binder Use After Free

http://seclists.org/fulldisclosure/2019/Oct/38
generic

Packet Storm

http://packetstormsecurity.com/files/156495/Android-Binder-Use-After-Free.html
generic

Packet Storm

http://packetstormsecurity.com/files/154911/Android-Binder-Use-After-Free.html

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulinux-image-virtual-lts-xenial (4.4.0.168.176) @ xenial2026-10-09ubuntu

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(6 across 5 ecosystems)
Debian:8(2)
PackageVulnerable rangeFix by version rangeDependents
linux3.16.36-1 ... 3.16.76-1 (69 versions)
  • every version up to 3.16.81-1: fixed in 3.16.81-1
—
linux-4.94.9.110-1~deb8u1, 4.9.144-3.1~deb8u1, 4.9.168-1~deb8u1, 4.9.189-3~deb8u1
  • every version up to 4.9.210-1~deb8u1: fixed in 4.9.210-1~deb8u1
—
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 4.15.4-1: fixed in 4.15.4-1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 4.15.4-1: fixed in 4.15.4-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 4.15.4-1: fixed in 4.15.4-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 4.15.4-1: fixed in 4.15.4-1
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

All Vendor Advisories

(1)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 91× in last 7d / 419× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 1,687 total refreshes for this CVE.

  1. 2026-10-09 23:29 UTCVendor advisory
  2. 2026-10-09 23:29 UTCGHSA enrichment
  3. 2026-10-09 19:47 UTCVendor advisory
  4. 2026-10-09 19:47 UTCGHSA enrichment
  5. 2026-10-09 16:04 UTCVendor advisory
  6. 2026-10-09 16:04 UTCGHSA enrichment
  7. 2026-10-09 12:22 UTCGHSA enrichment
  8. 2026-10-09 08:38 UTCVendor advisory
  9. 2026-10-09 08:38 UTCGHSA enrichment
  10. 2026-10-09 04:55 UTCVendor advisory
  11. 2026-10-09 04:55 UTCGHSA enrichment
  12. 2026-10-09 01:13 UTCVendor advisory
  13. 2026-10-09 01:13 UTCGHSA enrichment
  14. 2026-10-08 21:31 UTCVendor advisory
  15. 2026-10-08 21:31 UTCGHSA enrichment
  16. 2026-10-08 17:49 UTCEG score recompute
  17. 2026-10-08 17:49 UTCVendor advisory
  18. 2026-10-08 17:49 UTCGHSA enrichment
  19. 2026-10-08 16:37 UTCEPSS rescore
  20. 2026-10-08 14:04 UTCGHSA enrichment
  21. 2026-10-08 10:20 UTCVendor advisory
  22. 2026-10-08 10:20 UTCGHSA enrichment
  23. 2026-10-08 06:38 UTCGHSA enrichment
  24. 2026-10-08 02:56 UTCEG score recompute
  25. 2026-10-08 02:56 UTCVendor advisory
Show 75 more
  1. 2026-10-08 02:56 UTCGHSA enrichment
  2. 2026-10-07 23:43 UTCEPSS rescore
  3. 2026-10-07 23:14 UTCVendor advisory
  4. 2026-10-07 23:14 UTCGHSA enrichment
  5. 2026-10-07 19:32 UTCGHSA enrichment
  6. 2026-10-07 15:49 UTCGHSA enrichment
  7. 2026-10-07 12:02 UTCVendor advisory
  8. 2026-10-07 12:02 UTCGHSA enrichment
  9. 2026-10-07 08:19 UTCVendor advisory
  10. 2026-10-07 08:19 UTCGHSA enrichment
  11. 2026-10-07 04:34 UTCVendor advisory
  12. 2026-10-07 04:34 UTCGHSA enrichment
  13. 2026-10-07 00:52 UTCVendor advisory
  14. 2026-10-07 00:52 UTCGHSA enrichment
  15. 2026-10-06 21:10 UTCVendor advisory
  16. 2026-10-06 21:10 UTCGHSA enrichment
  17. 2026-10-06 17:28 UTCEG score recompute
  18. 2026-10-06 17:28 UTCVendor advisory
  19. 2026-10-06 17:28 UTCGHSA enrichment
  20. 2026-10-06 15:12 UTCEPSS rescore
  21. 2026-10-06 13:47 UTCVendor advisory
  22. 2026-10-06 13:47 UTCGHSA enrichment
  23. 2026-10-06 10:05 UTCVendor advisory
  24. 2026-10-06 10:05 UTCGHSA enrichment
  25. 2026-10-06 06:23 UTCVendor advisory
  26. 2026-10-06 06:23 UTCGHSA enrichment
  27. 2026-10-06 02:41 UTCVendor advisory
  28. 2026-10-06 02:41 UTCGHSA enrichment
  29. 2026-10-05 22:58 UTCVendor advisory
  30. 2026-10-05 22:58 UTCGHSA enrichment
  31. 2026-10-05 19:16 UTCGHSA enrichment
  32. 2026-10-05 15:33 UTCVendor advisory
  33. 2026-10-05 15:32 UTCGHSA enrichment
  34. 2026-10-05 11:50 UTCVendor advisory
  35. 2026-10-05 11:50 UTCGHSA enrichment
  36. 2026-10-05 08:09 UTCVendor advisory
  37. 2026-10-05 08:09 UTCGHSA enrichment
  38. 2026-10-05 04:27 UTCVendor advisory
  39. 2026-10-05 04:27 UTCGHSA enrichment
  40. 2026-10-05 00:44 UTCGHSA enrichment
  41. 2026-10-04 21:02 UTCVendor advisory
  42. 2026-10-04 21:02 UTCGHSA enrichment
  43. 2026-10-04 17:20 UTCVendor advisory
  44. 2026-10-04 17:20 UTCGHSA enrichment
  45. 2026-10-04 13:39 UTCVendor advisory
  46. 2026-10-04 13:39 UTCGHSA enrichment
  47. 2026-10-04 09:57 UTCVendor advisory
  48. 2026-10-04 09:57 UTCGHSA enrichment
  49. 2026-10-04 06:15 UTCVendor advisory
  50. 2026-10-04 06:15 UTCGHSA enrichment
  51. 2026-10-04 02:34 UTCVendor advisory
  52. 2026-10-04 02:34 UTCGHSA enrichment
  53. 2026-10-03 22:52 UTCVendor advisory
  54. 2026-10-03 22:52 UTCGHSA enrichment
  55. 2026-10-03 19:10 UTCVendor advisory
  56. 2026-10-03 19:10 UTCGHSA enrichment
  57. 2026-10-03 15:28 UTCEG score recompute
  58. 2026-10-03 15:28 UTCVendor advisory
  59. 2026-10-03 15:28 UTCGHSA enrichment
  60. 2026-10-03 14:22 UTCEPSS rescore
  61. 2026-10-03 11:46 UTCVendor advisory
  62. 2026-10-03 11:46 UTCGHSA enrichment
  63. 2026-10-03 08:01 UTCVendor advisory
  64. 2026-10-03 08:01 UTCGHSA enrichment
  65. 2026-10-03 04:17 UTCVendor advisory
  66. 2026-10-03 04:17 UTCGHSA enrichment
  67. 2026-10-03 00:35 UTCVendor advisory
  68. 2026-10-03 00:35 UTCGHSA enrichment
  69. 2026-10-02 20:53 UTCVendor advisory
  70. 2026-10-02 20:53 UTCGHSA enrichment
  71. 2026-10-02 17:11 UTCEG score recompute
  72. 2026-10-02 17:11 UTCVendor advisory
  73. 2026-10-02 17:11 UTCGHSA enrichment
  74. 2026-10-02 13:29 UTCVendor advisory
  75. 2026-10-02 13:29 UTCGHSA enrichment

Publicly available exploits

(10 references)

Working exploit code is in the public domain (1 Metasploit module) (7 GitHub PoCs) (2 Exploit-DB entries). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • Exploit-DBEDB-48129✓ verified
    First seen Feb 24, 2020

    Android Binder - Use-After-Free (Metasploit)

    Open source ↗
  • Exploit-DBEDB-47463✓ verified
    First seen Oct 4, 2019

    Android - Binder Driver Use-After-Free

    Open source ↗
  • Metasploitexploit/android/local/binder_uaf✓ verified
    First seen Sep 26, 2019

    Android Binder Use-After-Free Exploit

    Open source ↗
  • GitHub PoCflipphoneguy/root-sonim-xp3800
    First seen Jun 30, 2026

    app that ports CVE-2019-2215 to arm32 and mounts a su binary to /sbin with denylist + root app installer. firehose/Magisk guide included

    Open source ↗
  • GitHub PoC0xbinder/android-kernel-exploitation-lab
    First seen Mar 13, 2025

    This lab guides you through setting up an environment to explore CVE-2019-2215, a critical Android kernel vulnerability in the binder subsystem.

    Open source ↗
  • GitHub PoCR0rt1z2/huawei-unlock
    First seen May 20, 2024

    Unlock your Huawei device with ADB (CVE-2019-2215)

    Open source ↗
  • GitHub PoCstevejubx/CVE-2019-2215
    First seen Nov 5, 2023

    Android Kernel Vulnerability (CVE-2019-2215) temporary root PoC

    Open source ↗
  • GitHub PoCc3r34lk1ll3r/CVE-2019-2215
    First seen Oct 27, 2020

    PoC for old Binder vulnerability (based on P0 exploit)

    Open source ↗
  • GitHub PoCsharif-dev/AndroidKernelVulnerability
    First seen Jun 7, 2020

    Triggering and Analyzing Android Kernel Vulnerability CVE-2019-2215

    Open source ↗
  • GitHub PoCqre0ct/android-kernel-exploitation-ashfaq-CVE-2019-2215
    First seen Apr 25, 2020

    android-kernel-exploitation-ashfaq-CVE-2019-2215 docker setup for mac users

    Open source ↗

Related CVEs(same product + same vendor + same CWE)

Frequently asked(6)

What is CVE-2019-2215?
CVE-2019-2215 is a critical vulnerability published on October 11, 2019. 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…
When was CVE-2019-2215 disclosed?
CVE-2019-2215 was first published on October 11, 2019, with the most recent update on October 24, 2025. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2019-2215 actively exploited?
Yes. CISA added CVE-2019-2215 to the Known Exploited Vulnerabilities catalog on November 3, 2021, affecting Android Android Kernel. KEV listing indicates confirmed exploitation in the wild; this CVE warrants immediate attention. A fix is available. Apply it.
What is the CVSS score of CVE-2019-2215?
CVE-2019-2215 has a CVSS v3 base score of 7.8 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 9.0 (CRITICAL).
Which products are affected by CVE-2019-2215?
CVE-2019-2215 affects Android Android Kernel. The affected packages EchelonGraph has on record, with version ranges, are listed in the Affected Packages section of this page.
How do I remediate CVE-2019-2215?
A fix for CVE-2019-2215 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2019-2215

Explore →

Is Your Infrastructure Affected by CVE-2019-2215?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs