CVE-2022-20009 json
In various functions of the USB gadget subsystem, there is a possible out of bounds write due to a missing bounds check.
published 4y ago modified 4mo ago also EUVD-2022-25269
- cvss
- 6.8
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.4%
- EPSS 0.4% chance of exploitation in 30 days, percentile 29%
- public exploits
- 0
- none known
Summary
In various functions of the USB gadget subsystem, there is a possible out of bounds write due to a missing 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-213172319References: Upstream kernel
Patch / fix
- linux Ubuntu 18.04 LTS 4.15.0-177.186
- linux Ubuntu 20.04 LTS 5.4.0-110.124
- linux-aws Ubuntu 18.04 LTS 4.15.0-1128.137
- linux-aws Ubuntu 20.04 LTS 5.4.0-1073.78
- linux-gcp Ubuntu 20.04 LTS 5.4.0-1073.78
- linux-gke Ubuntu 20.04 LTS 5.4.0-1071.76
- linux-ibm Ubuntu 20.04 LTS 5.4.0-1021.23
- linux-iot Ubuntu 20.04 LTS 5.4.0-1004.6
ubuntu advisories UBUNTU-CVE-2022-20009
Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
Is CVE-2022-20009 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerExploit prediction
0.35% chance of exploitation in the next 30 days, higher than 29% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 6.8 | CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 7.2 | AV:L/AC:L/Au:N/C:C/I:C/A:C |
Affected products
- n/a Android
Classification
- Weakness
-
- CWE-787 Out-of-bounds Write
References
-
source.android.com
/security/bulletin/2022-05-01
patch, vendor-advisory
Sources
- CVE List CVE-2022-20009
- NVD CVE-2022-20009
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.