CVE-2022-20409

In io_identity_cow of io_uring.c, there is a possible way to corrupt memory due to a use after free. This could lead to local escalation of privilege with System execution privileges needed. User interaction is not needed for exploitation.Product: AndroidVersions: Android kernelAndroid ID: A-238177383References: Upstream kernel

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

CVE-2022-20409 is rated Low Risk (36.6/100): CVSS Medium severity, with low exploitation likelihood (EPSS 0.56%). Monitor for updates and reassess as exploit intelligence or EPSS changes.

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-20409

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-15 5.61% 0.56% -5.05%
2 2026-06-07 5.76% 5.61% -0.15%
3 2026-05-25 — 5.76% —

Full EPSS history (26 records total)

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

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
6.7 3.1 MEDIUM
CVSS:3.1/AV:L/AC:L/PR:H/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:H)
They need powerful rights—admin, root, or similar—before this pays off.
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.
 0.8 5.9 [email protected]

Weakness enumeration for CVE-2022-20409

OS Trackers for CVE-2022-20409

vendor priority summary link
debian not yet assigned CVE-2022-20409 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-20409
ubuntu medium CVE-2022-20409 medium priority: Ubuntu including 122 source packages (linux, linux-allwinner, …), 927 status rows across 10 suites (bionic, focal, jammy, kinetic, lunar, mantic, noble, trusty, upstream, xenial): DNE 598, not-affected 159, ignored 91, released 79. https://ubuntu.com/security/CVE-2022-20409

Affected software / configurations for CVE-2022-20409

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

References for CVE-2022-20409

cvelogic Threat Intelligence