CVE-2022-39127: Medium severity android vulnerability
Published Oct 14, 2022
·Updated
In sensor driver, there is a possible out of bounds write due to a missing bounds check. This could lead to local denial of service in kernel.
Affected Software
32 affected components
Google Android=10.0
Google Android=11.0
Google Android=12.0
UNISOC S8000
UNISOC Sc7731e
UNISOC Sc9832e
UNISOC Sc9863a
UNISOC T310
UNISOC T606
UNISOC T610
UNISOC T612
UNISOC T616
UNISOC T618
UNISOC T760
UNISOC T770
UNISOC T820
All of the following
Any of the following
Google Android=10.0
Google Android=11.0
Google Android=12.0
Any of the following
UNISOC S8000
UNISOC Sc7731e
UNISOC Sc9832e
UNISOC Sc9863a
UNISOC T310
UNISOC T606
UNISOC T610
UNISOC T612
UNISOC T616
UNISOC T618
UNISOC T760
UNISOC T770
UNISOC T820
Event History
Oct 14, 2022
CVE Published
via MITRE·12:00 AM
Data Sourced
via MITRE·12:00 AM
DescriptionWeakness
Frequently Asked Questions
1
What is the severity of CVE-2022-39127?
CVE-2022-39127 has a severity rating that indicates potential for local denial of service due to an out of bounds write issue in the sensor driver.
2
How do I fix CVE-2022-39127?
To fix CVE-2022-39127, it is recommended to update the affected Android versions (10.0, 11.0, and 12.0) to the latest security patches provided by Google.
3
Which Android versions are affected by CVE-2022-39127?
CVE-2022-39127 affects Android versions 10.0, 11.0, and 12.0.
4
What are the potential impacts of CVE-2022-39127?
The potential impacts of CVE-2022-39127 include local denial of service which could disrupt system functionality.
5
Is any Unisoc device impacted by CVE-2022-39127?
No, the listed Unisoc devices such as SC7731, SC9832E, and others are noted to be non-vulnerable to CVE-2022-39127.