Skip to content
Server Security Center
KEVhigh7.8

CVE-2020-0041: Android Kernel Out-of-Bounds Write

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)
3.2%
higher than 88.3% of all CVEs
Added to CISA KEV
2021-11-03
US federal due date 2022-05-03
Ubuntu priority
high

CVE-2020-0041 explained

CVE-2020-0041 is an out-of-bounds write in binder_transaction of binder.c in the Linux kernel, caused by an incorrect bounds check. A local user can use it to escalate privileges without user interaction. It is listed in the CISA Known Exploited Vulnerabilities catalog, and Ubuntu rates it high priority.

Impact

An attacker who already has low-privileged local access can write outside intended memory bounds in the kernel and gain elevated privileges. No user interaction and no additional execution privileges are needed, and attack complexity is low. Successful exploitation can fully compromise confidentiality, integrity and availability of the affected system. The attack cannot be carried out remotely without local access.

Who is affected

On Ubuntu 18.04 LTS, fixed versions exist for linux-hwe (5.3.0-40.32~18.04.1), linux-azure-5.3 (5.3.0-1013.14~18.04.1), linux-gcp-5.3 and linux-gke-5.3 (5.3.0-1012.13~18.04.1) and linux-raspi2-5.3 (5.3.0-1018.20~18.04.1). No fixed version is published for linux-azure-edge, linux-gcp-edge and linux-hwe-edge on 18.04, for linux-hwe-edge on end-of-life 16.04, for linux-azure-fde, linux-gke, linux-gkeop and linux-gkeop-5.15 on 20.04, for linux-intel-iot-realtime, linux-realtime and linux-riscv on 22.04, or for linux-raspi-realtime on 24.04.

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

Official description

In binder_transaction of binder.c, there is a possible out of bounds write due to an incorrect bounds check. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.Product: AndroidVersions: Android kernelAndroid ID: A-145988638References: Upstream kernel

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
    • Android 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.

What to do

  1. Identify which kernel source package and release each host runs.
  2. On Ubuntu 18.04 LTS, install the fixed kernel version for your flavour; ongoing fixes for this release require Ubuntu Pro (ESM).
  3. Reboot into the updated kernel so the fix takes effect.
  4. Upgrade Ubuntu 16.04 LTS hosts to a supported release, since it is end of life.
  5. For flavours without a fixed version, track the Ubuntu advisory and update once a fix is published.

Several kernel flavours on Ubuntu 18.04, 20.04, 22.04 and 24.04 have no fixed version published. Where possible, switch to a kernel flavour with a fix. Restrict local and shell access to trusted users, and do not run untrusted code on affected hosts. Monitor the Ubuntu advisory for updates. Ubuntu 16.04 LTS is end of life; upgrade those systems.

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.

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-20 Improper Input Validation

Questions about CVE-2020-0041

Can this be exploited remotely?
No. The attack vector is local. An attacker needs low-privileged local access, but no user interaction is required.
Is this vulnerability exploited in practice?
Yes. CISA added it to the Known Exploited Vulnerabilities catalog on 2021-11-03, with required action to apply updates per vendor instructions. Ransomware use is listed as unknown.
Is installing the updated package enough?
No. The system keeps running the old kernel until it is rebooted into the updated kernel.

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.