CVE-2022-20369

Description

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

Category

6.7
CVSS
Severity: Medium
CVSS 3.1 •
EPSS 0.04%
Vendor Advisory android.com
Affected: n/a Android
Published at:
Updated at:

References

Link Tags
https://source.android.com/security/bulletin/pixel/2022-08-01 patch vendor advisory
https://lists.debian.org/debian-lts-announce/2022/12/msg00034.html third party advisory mailing list

Frequently Asked Questions

What is the severity of CVE-2022-20369?
CVE-2022-20369 has been scored as a medium severity vulnerability.
How to fix CVE-2022-20369?
To fix CVE-2022-20369, make sure you are using an up-to-date version of the affected component(s) by checking the vendor release notes. As for now, there are no other specific guidelines available.
Is CVE-2022-20369 being actively exploited in the wild?
As for now, there are no information to confirm that CVE-2022-20369 is being actively exploited. According to its EPSS score, there is a ~0% probability that this vulnerability will be exploited by malicious actors in the next 30 days.
What software or system is affected by CVE-2022-20369?
CVE-2022-20369 affects n/a Android.
This platform uses data from the NIST NVD, MITRE CVE, MITRE CWE, First.org and CISA KEV but is not endorsed or certified by these entities. CVE is a registred trademark of the MITRE Corporation and the authoritative source of CVE content is MITRE's CVE web site. CWE is a registred trademark of the MITRE Corporation and the authoritative source of CWE content is MITRE's CWE web site.
© 2025 Under My Watch. All Rights Reserved.