CVE-2020-0041

Exp

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

Published: 2020-03-10 Last update: 2025-10-23 Assigner: [email protected] Source: [email protected]
NVD Status：Analyzed，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2020-0041 is rated Critical Active Threat (92.4/100): CVSS High severity, with high exploitation likelihood (EPSS 23.86%, 96th percentile). CISA KEV confirms active exploitation (added 2021-11-03) affecting Android / Android Kernel. a weakness (CWE-20) Unauthenticated remote administrative access may be possible. EPSS rose +2.62% over the last day, indicating growing attacker interest. The CISA remediation deadline has passed—treat as an emergency patch priority.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

CISA KEV Record for CVE-2020-0041

Name: Android Kernel Out-of-Bounds Write Vulnerability · CISA KEV detail

Exploit added: 2021-11-03

Action due: 2022-05-03

Required action: Apply updates per vendor instructions.

Exploit prediction scoring system (EPSS) score for CVE-2020-0041

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-01-26 21.24% 23.86% +2.62%
2 2025-12-27 16.26% 21.24% +4.98%
3 2025-12-16 — 16.26% —

Full EPSS history (33 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2020-0041

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
7.8 3.1 HIGH
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H Click to expand
Attack vector (AV:L)
They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L)
A normal user session is enough; they don’t have to be admin.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 1.8 5.9 [email protected]
7.8 3.1 HIGH
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H Click to expand
Attack vector (AV:L)
They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L)
A normal user session is enough; they don’t have to be admin.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 1.8 5.9 134c704f-9b21-4f2e-91b3-4a467353bcc0
7.2 2.0 HIGH
AV:L/AC:L/Au:N/C:C/I:C/A:C Click to expand
Access vector (AV:L)
Requires local access to the target system.
Access complexity (AC:L)
Exploitation conditions are straightforward and predictable.
Authentication (AU:N)
No authentication is required.
Confidentiality impact (C:C)
Complete confidentiality impact.
Integrity impact (I:C)
Complete integrity impact.
Availability impact (A:C)
Complete availability impact.
 3.9 10.0 [email protected]

Weakness enumeration for CVE-2020-0041

OS Trackers for CVE-2020-0041

vendor priority summary link
debian not yet assigned CVE-2020-0041 not yet assigned priority: Debian including 1 source packages (linux), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 5. https://security-tracker.debian.org/tracker/CVE-2020-0041
ubuntu high CVE-2020-0041 high priority: Ubuntu including 79 source packages (linux, linux-aws, …), 688 status rows across 10 suites (bionic, eoan, focal, groovy, jammy, noble, oracular, trusty, upstream, xenial): DNE 445, not-affected 141, released 91, ignored 11. https://ubuntu.com/security/CVE-2020-0041

Affected software / configurations for CVE-2020-0041

Vendor Product Version Raw CPE
google android — cpe:2.3:o:google:android:-:*:*:*:*:*:*:*

References for CVE-2020-0041

cvelogic Threat Intelligence