Skip to content
Server Security Center
KEVhigh7.8

CVE-2019-2215: Android Kernel Use-After-Free

Android Kernel · listed in the CISA catalog of actively exploited vulnerabilities since 2021-11-03.

CVSS v3.1 (CVE record)
7.8
high
EPSS (exploit probability, 30 days)
72%
higher than 99.4% of all CVEs
Added to CISA KEV
2021-11-03
US federal due date 2022-05-03
Ubuntu priority
high

CVE-2019-2215 explained

CVE-2019-2215 is a use-after-free in binder.c in the kernel. It lets a local application elevate its privileges to the Linux kernel. CISA lists it as a known exploited vulnerability, and Ubuntu rates it high priority, so affected kernels should be updated promptly.

Impact

An attacker who can run code locally with low privileges can gain kernel-level control. That means full loss of confidentiality, integrity and availability. No user interaction is needed. Exploitation requires either a malicious local application or a separate vulnerability in a network-facing application that gives the attacker local code execution.

Who is affected

The facts list Ubuntu 16.04 LTS, source package linux, as affected. It is fixed in 4.4.0-168.197 in the standard archive. Ubuntu 16.04 LTS is end of life. Further Ubuntu kernel flavours are listed on the page; check them for your installed kernel.

Written with AI from the data on this page and checked against it automatically.

Official description

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

CISA required action: Apply updates per vendor instructions.

CISA notes

Upstream versions (CVE record)

From the CVE record published by the vendor or CVE numbering authority.

  • Android
    Affected
    • Kernel
    Fixed in
    not stated

    Version statement as published by the CNA (free text).

Ubuntu and Debian releases

A server is vulnerable if it has a package built from the listed source package installed in a version lower than the fixed version for its release.

15 more Ubuntu kernel flavours (cloud, HWE, low-latency, real-time …) – 18 release entries
  • 24.04 linux-raspi-realtime: no fixed version published
  • 22.04 linux-intel-iot-realtime: no fixed version published
  • 22.04 linux-realtime: no fixed version published
  • 22.04 linux-riscv: no fixed version published
  • 20.04 linux-azure-fde: no fixed version published
  • 20.04 linux-gke: no fixed version published
  • 20.04 linux-riscv: no fixed version published
  • 18.04 linux-snapdragon: 4.15.0-1053.57
  • 16.04 linux-aws: 4.4.0-1098.109
  • 16.04 linux-azure: 4.15.0-1013.13~16.04.2
  • 16.04 linux-gcp: 4.15.0-1014.14~16.04.1
  • 16.04 linux-hwe: 4.15.0-24.26~16.04.1
  • 16.04 linux-hwe-edge: no fixed version published
  • 16.04 linux-kvm: 4.4.0-1062.69
  • 16.04 linux-raspi2: 4.4.0-1125.134
  • 16.04 linux-snapdragon: 4.4.0-1129.137
  • 14.04 linux-aws (Pro): 4.4.0-1058.62
  • 14.04 linux-lts-xenial (Pro): 4.4.0-168.197~14.04.1

What to do

  1. Identify which kernel package and flavour each Ubuntu 16.04 LTS system runs.
  2. Update the linux kernel to 4.4.0-168.197 or later.
  3. Reboot so the fixed kernel is actually running.
  4. Check the page for other affected kernel flavours and update them too.
  5. Plan an upgrade away from Ubuntu 16.04 LTS, which is end of life.

Written with AI from the data on this page and checked against it automatically.

Check and fix on a server

Kernel fixes arrive as a new kernel package (new ABI) through the metapackages, so upgrade the whole system and boot into the new kernel.

1. Show the running kernel and the version of its package

uname -r && dpkg-query -W -f='${Version}\n' "linux-image-$(uname -r)"

2. Compare with the fixed version for your release and kernel flavour from the table

I=INSTALLED_VERSION; F=FIXED_VERSION   # replace both
dpkg --compare-versions "$I" lt "$F"; case $? in 0) echo vulnerable ;; 1) echo "fixed or newer" ;; *) echo "check the versions" ;; esac

3. Install the new kernel, then reboot (or apply a livepatch)

sudo apt update && sudo apt full-upgrade && sudo reboot

On Debian, signed kernel images come from the linux-signed-* source packages; the version to compare is the same.

Rows marked “fix via Ubuntu Pro”: these fixes are only installable with an Ubuntu Pro subscription (ESM). Attach the machine first (sudo pro attach, then sudo pro enable esm-infra esm-apps), then run the commands above.

CISA's assessment (SSVC)

Exploitation
Exploited in the wild
Automatable
No – each attack needs manual steps
Technical impact
Total – full control of the component or total information disclosure

Weakness: CWE-416 Use After Free

Questions about CVE-2019-2215

Is this vulnerability exploited in practice?
Yes. CISA added CVE-2019-2215 to its Known Exploited Vulnerabilities catalog on 2021-11-03. Its required action is to apply updates per vendor instructions. Whether it has been used in ransomware is listed as unknown.
Can it be exploited remotely?
Not directly. The attack vector is local. An attacker needs a malicious local application, or a separate vulnerability in a network-facing application, to run code on the system first.
Is installing the updated package enough?
No. The system keeps running the old kernel until it is rebooted into the fixed version, 4.4.0-168.197 or later.

Written with AI from the data on this page and checked against it automatically.

References

Data: CISA Known Exploited Vulnerabilities (public domain) · CVE Program records incl. CISA ADP enrichment · OSV.dev (CC BY 4.0) incl. Ubuntu and Debian security data · FIRST EPSS · endoflife.date. Updated automatically – facts last changed 2026-11-21. Always confirm with the vendor's or distribution's advisory before patching.