What is 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
1 affected-product entry is recorded, across 1 vendor, listed below. The identifier was first published 1482 days ago.
Severity and exploitation probability
- EPSS (FIRST)
- 0.7% probability of exploitation in the next 30 days, higher than 52.7% of all scored CVEs
- CISA KEV
- Not listed in the CISA Known Exploited Vulnerabilities catalog
- Threadlinqs priority
- 4.1/10 — a Threadlinqs composite of the CVSS base score, the EPSS percentile and public exploit availability
- Published
- 2022-10-11, last modified 2024-08-03
Is CVE-2022-20421 being exploited?
Weaponised exploit code for CVE-2022-20421 is publicly available. 3 public proof-of-concept repositories are tracked for this identifier. It currently carries a trending score of 26 in the Threadlinqs vulnerability feed.
- 0xkol/badspin (github)
- sandiyochristan/oo (github)
- trickest/cve (trickest)
Affected products and versions
- (vendor unspecified): Android
How to fix CVE-2022-20421
No vendor patch reference has been recorded for CVE-2022-20421 in the tracked sources. Follow the references below for a fix, and treat the products listed above as exposed until the vendor states otherwise.
Threat activity tracking CVE-2022-20421
1 tracked threat in the Threadlinqs corpus references CVE-2022-20421, either in the campaign’s CVE list or as an indicator on the campaign record.
Sources
Enriched from CVE.org, FIRST EPSS, GitHub Security Advisories, public proof-of-concept repositories. Last verified by Threadlinqs on .