CVE-2022-20421

In binder_inc_ref_for_node of binder.c, there is a possible way to corrupt memory due to a use after free. 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-239630375References: Upstream kernel

Published: 2022-10-11 Last update: 2024-11-21 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2022-20421 is rated Moderate Risk (63.3/100): CVSS High severity, with high exploitation likelihood (EPSS 5.86%, 91th percentile). EPSS ranks this CVE among the most likely to be exploited in the near term. High exploitation likelihood—assess exposure and prioritize remediation.

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

Exploit prediction scoring system (EPSS) score for CVE-2022-20421

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-06-07 5.57% 5.86% +0.29%
2 2026-05-25 5.43% 5.57% +0.14%
3 2026-05-04 — 5.43% —

Full EPSS history (29 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2022-20421

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]

Weakness enumeration for CVE-2022-20421

OS Trackers for CVE-2022-20421

vendor priority summary link
debian not yet assigned CVE-2022-20421 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-2022-20421
redhat medium — https://access.redhat.com/security/cve/CVE-2022-20421
suse high CVE-2022-20421 severity important: SUSE including 13 source package names (cluster-md-kmp-default, dlm-kmp-default, …), 138 product×package rows across 52 product lines (SUSE CaaS Platform 4.0, SUSE Enterprise Storage 6, … (52 product lines)): Known Not Affected 138. https://www.suse.com/security/cve/CVE-2022-20421/
ubuntu medium CVE-2022-20421 medium priority: Ubuntu including 167 source packages (linux, linux-allwinner, …), 1774 status rows across 13 suites (bionic, focal, jammy, kinetic, lunar, mantic, noble, oracular, plucky, questing, trusty, upstream, xenial): DNE 1316, released 211, not-affected 162, ignored 85. https://ubuntu.com/security/CVE-2022-20421

Affected software / configurations for CVE-2022-20421

Vendor Product Version Raw CPE
google android — cpe:2.3:o:google:android:-:*:*:*:*:*:*:*
debian debian_linux 10.0 cpe:2.3:o:debian:debian_linux:10.0:*:*:*:*:*:*:*
debian debian_linux 11.0 cpe:2.3:o:debian:debian_linux:11.0:*:*:*:*:*:*:*

References for CVE-2022-20421

cvelogic Threat Intelligence