Google Android v4l2-mem2mem.c v4l2_m2m_querybuf out-of-bounds write
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.6 | $5k-$25k | 0.00 |
Summary
A vulnerability was found in Google Android. It has been classified as critical. This affects the function v4l2_m2m_querybuf of the file v4l2-mem2mem.c. The manipulation leads to out-of-bounds write.
This vulnerability is referenced as CVE-2022-20369. The attack can only be performed from a local environment. No exploit is available.
It is suggested to install a patch to address this issue.
Details
A vulnerability was found in Google Android (Smartphone Operating System) (unknown version). It has been rated as critical. This issue affects the function v4l2_m2m_querybuf of the file v4l2-mem2mem.c. The manipulation with an unknown input leads to a out-of-bounds write vulnerability. Using CWE to declare the problem leads to CWE-787. The product writes data past the end, or before the beginning, of the intended buffer. Impacted is confidentiality, integrity, and availability. The summary by CVE is:
In v4l2_m2m_querybuf of v4l2-mem2mem.c, there is a possible out of bounds write due to improper input validation. 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-223375145References: Upstream kernel
The weakness was published 08/11/2022 as A-223375145. The advisory is shared at source.android.com. The identification of this vulnerability is CVE-2022-20369 since 10/14/2021. Technical details are known, but no exploit is available. The price for an exploit might be around USD $5k-$25k at the moment (estimation calculated on 04/12/2026). It is expected to see the exploit prices for this product increasing in the near future.
The vulnerability scanner Nessus provides a plugin with the ID 239841 (TencentOS Server 4: kernel (TSSA-2024:0960)), which helps to determine the existence of the flaw in a target environment.
Applying a patch is able to eliminate this problem.
The vulnerability is also documented in the databases at Tenable (239841) and EUVD (EUVD-2022-25629). Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Type
Vendor
Name
License
Website
- Vendor: https://www.google.com/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.7VulDB Meta Temp Score: 6.6
VulDB Base Score: 6.7
VulDB Temp Score: 6.4
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 6.7
NVD Vector: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
Exploiting
Class: Out-of-bounds writeCWE: CWE-787 / CWE-119
CAPEC: 🔍
ATT&CK: 🔍
Physical: Partially
Local: Yes
Remote: No
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Nessus ID: 239841
Nessus Name: TencentOS Server 4: kernel (TSSA-2024:0960)
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: PatchStatus: 🔍
0-Day Time: 🔍
Timeline
10/14/2021 🔍08/11/2022 🔍
08/11/2022 🔍
04/12/2026 🔍
Sources
Vendor: google.comAdvisory: A-223375145
Status: Confirmed
CVE: CVE-2022-20369 (🔍)
GCVE (CVE): GCVE-0-2022-20369
GCVE (VulDB): GCVE-100-206225
EUVD: 🔍
scip Labs: https://www.scip.ch/en/?labs.20150917
Entry
Created: 08/11/2022 22:12Updated: 04/12/2026 20:39
Changes: 08/11/2022 22:12 (42), 09/10/2022 12:23 (10), 06/20/2025 00:52 (16), 04/12/2026 20:39 (2)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.