CVE-2022-20064: High severity android vulnerability
Published Apr 11, 2022
·Updated
In ccci, there is a possible leak of kernel pointer due to an incorrect bounds check. This could lead to local information disclosure with System execution privileges needed. User interaction is not needed for exploitation. Patch ID: ALPS06108617; Issue ID: ALPS06108617.
Affected Software
39 affected components
Google Android=10.0
Google Android=11.0
Google Android=12.0
MediaTek Mt6580
MediaTek Mt6737
MediaTek Mt6739
MediaTek Mt6761
MediaTek Mt6762
MediaTek Mt6763
MediaTek Mt6765
MediaTek Mt6768
MediaTek Mt6769
MediaTek Mt6779
MediaTek Mt6781
MediaTek Mt6785
MediaTek Mt6789
MediaTek Mt6833
MediaTek Mt6853
MediaTek Mt6873
MediaTek Mt6875
MediaTek Mt6877
MediaTek Mt6879
MediaTek Mt6883
MediaTek Mt6885
MediaTek Mt6889
MediaTek Mt6893
MediaTek Mt6895
MediaTek Mt6983
MediaTek Mt6985
MediaTek Mt8321
MediaTek Mt8667
MediaTek Mt8675
MediaTek Mt8765
MediaTek Mt8766
MediaTek Mt8768
MediaTek Mt8786
MediaTek Mt8788
MediaTek Mt8789
MediaTek Mt8797
Event History
Apr 11, 2022
CVE Published
via MITRE·07:37 PM
Data Sourced
via MITRE·07:37 PM
DescriptionWeakness
Frequently Asked Questions
1
What is the severity of CVE-2022-20064?
The severity of CVE-2022-20064 is classified as high due to possible local information disclosure.
2
How do I fix CVE-2022-20064?
To fix CVE-2022-20064, apply the patch provided in the patch ID ALPS06108617.
3
Who is affected by CVE-2022-20064?
CVE-2022-20064 affects devices running Google Android versions 10.0, 11.0, and 12.0.
4
Does CVE-2022-20064 require user interaction for exploitation?
No, CVE-2022-20064 does not require user interaction for exploitation.
5
What types of vulnerabilities are indicated by CVE-2022-20064?
CVE-2022-20064 indicates a possible leak of kernel pointers due to an incorrect bounds check.