CVE-2022-39124: 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-39124?
CVE-2022-39124 has a severity that could lead to local denial of service due to an out of bounds write.
2
How do I fix CVE-2022-39124?
To fix CVE-2022-39124, ensure that the affected Android versions are updated to the latest security patch provided by Google.
3
What versions of Android are affected by CVE-2022-39124?
CVE-2022-39124 affects Android versions 10.0, 11.0, and 12.0.
4
What is the impact of CVE-2022-39124?
The impact of CVE-2022-39124 is a potential local denial of service in the kernel due to a missing bounds check.
5
Is there a workaround for CVE-2022-39124?
Currently, the recommended approach for CVE-2022-39124 is to apply the necessary updates rather than relying on a workaround.