CVE-2019-2215

CRITICALNVD 7.89.0
EchelonGraph scoreHIGH confidence

“▲” beside the score: it is higher than NVD's CVSS score.

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. The 9.0 is the floor for confirmed exploitation, not an impact rating: this CVE's impact severity (EG Severity) is CVSS 7.8 HIGH under GitHub Security Advisory CVSS. Confidence: HIGH.

Triggered by: CISA KEV (actively exploited)
Sources: CISA Known Exploited Vulnerabilities catalog, EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — 4 sources updated this weekExploited in the wild

Also known asEUVD-2019-11857 (ENISA EUVD) · GHSA-m7g6-9cwp-6jgm (GitHub Security Advisories)Source: ENISA EUVD

9.0EG
EchelonGraph verdictPatch nowTreat as an emergency — this is being exploited.
  • Actively exploited in the wild (CISA-KEV) — the reason this is sooner than the SSVC decision on this page at low or medium mission impact
CISA-KEV: ExploitedEPSS PROB: 72%CVSS: 7.8Exploit: Metasploit · Exploit-DB (verified) · other public PoCExposed 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
75
EG Risk 75/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity78% × 45%
Impact severity (EG Severity): CVSS 7.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation100% × 40%
Fixed at 100% for a CISA KEV listing: EchelonGraph's rule.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Attend at medium and Act at high mission impact.
Exploitation active (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
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

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (9.0): severity, escalated by confirmed exploitation. This CVE's 9.0 is the CISA KEV floor for confirmed exploitation, not an impact rating: its impact severity (EG Severity) is CVSS 7.8 HIGH.

EG Severity
7.8 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
72% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-01). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
CISA KEV and EG-KEV Tier 1 (exploited in the wild)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Attend at medium mission impactTrack at low, Attend at medium and Act at high mission impact.CISA BOD 26-04: 3 days & forensic triage if the affected system is publicly exposed; 14 days if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track 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). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)3 days & forensic triage if the affected system is publicly exposed; 14 days if it is not.

The score's inputs: In CISA KEV yes (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

CISA required action“Apply updates per vendor instructions.”

Quoted verbatim from CISA's Known Exploited Vulnerabilities catalog. CISA directs it at US federal civilian executive branch agencies under Binding Operational Directive (BOD) 26-04, which replaced BOD 22-01 on 10 June 2026; it is not EchelonGraph's advice. CISA's notes: https://nvd.nist.gov/vuln/detail/CVE-2019-2215

Published

October 11, 2019

Last Modified

October 24, 2025

Advisory Details (10)

Auto-updated Nov 2, 2026
⚠️ Actively exploited (CISA KEV, CISA Vulnrichment). Patch available.
Web page

Android Security Bulletin—October 2019  |  Android Open Source Project

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

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

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

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

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

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

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

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

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

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

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

Patch Availability(1)

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

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 24× in last 7d / 187× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 1,795 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 1,695 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Publicly available exploits

(14 references, 10 shown)

Public exploit code is referenced for this CVE (1 Metasploit module, 2 Exploit-DB entries, 11 GitHub PoCs). Defenders should treat patch urgency accordingly.

  • Exploit-DBEDB-48129✓ verified
    Published Feb 24, 2020

    Android Binder - Use-After-Free (Metasploit)

    Open source ↗
  • Metasploitexploit/android/local/binder_uaf✓ verified
    Published Feb 23, 2020

    Android Binder Use-After-Free Exploit

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

    Android - Binder Driver Use-After-Free

    Open source ↗
  • GitHub PoCflipphoneguy/root-sonim-xp3800
    Published 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
    Published 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
    Published May 20, 2024

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

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

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

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

    PoC for old Binder vulnerability (based on P0 exploit)

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

    Triggering and Analyzing Android Kernel Vulnerability CVE-2019-2215

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

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

    Open source ↗

Frequently asked(6)

What is CVE-2019-2215?
CVE-2019-2215 is a critical-severity vulnerability; its CVE record was 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 the CVE record for CVE-2019-2215 published?
The CVE record for CVE-2019-2215 was published on October 11, 2019. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 24, 2025; the record at its source may have been updated since.
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.