CVE-2022-20016: Medium severity android vulnerability
Published Jan 4, 2022
·Updated
In vow driver, there is a possible memory corruption due to improper locking. This could lead to local escalation of privilege with System execution privileges needed. User interaction is not needed for exploitation. Patch ID: ALPS05862986; Issue ID: ALPS05862986.
Affected Software
36 affected components
All of the following
Any of the following
Google Android=10.0
Google Android=11.0
Any of the following
MediaTek Mt6781
MediaTek Mt6785
MediaTek Mt6833
MediaTek Mt6853
MediaTek Mt6853t
MediaTek Mt6873
MediaTek Mt6877
MediaTek Mt6883
MediaTek Mt6885
MediaTek Mt6889
MediaTek Mt6891
MediaTek Mt6893
MediaTek Mt8185
MediaTek Mt8789
MediaTek Mt8791
MediaTek Mt8797
Google Android=10.0
Google Android=11.0
MediaTek Mt6781
MediaTek Mt6785
MediaTek Mt6833
MediaTek Mt6853
MediaTek Mt6853t
MediaTek Mt6873
MediaTek Mt6877
MediaTek Mt6883
MediaTek Mt6885
MediaTek Mt6889
MediaTek Mt6891
MediaTek Mt6893
MediaTek Mt8185
MediaTek Mt8789
MediaTek Mt8791
MediaTek Mt8797
Event History
Jan 4, 2022
CVE Published
via MITRE·03:56 PM
Data Sourced
via MITRE·03:56 PM
DescriptionWeakness
Data Sourced
via NVD·04:15 PM
DescriptionSeverityWeaknessAffected Software
Frequently Asked Questions
1
What is the severity of CVE-2022-20016?
CVE-2022-20016 has a severity level that allows for local escalation of privilege, requiring system execution privileges.
2
How do I fix CVE-2022-20016?
To fix CVE-2022-20016, you need to apply the patch identified as ALPS05862986.
3
What consequences can result from exploiting CVE-2022-20016?
Exploitation of CVE-2022-20016 can lead to memory corruption, potentially allowing unauthorized users to gain elevated privileges.
4
Is user interaction required to exploit CVE-2022-20016?
No, user interaction is not needed for the exploitation of CVE-2022-20016.
5
Which versions of Google Android are affected by CVE-2022-20016?
CVE-2022-20016 affects Google Android versions 10.0 and 11.0.