CVE-2022-26447: Critical severity android vulnerability
Published Sep 6, 2022
·Updated
In BT firmware, there is a possible out of bounds write due to a missing bounds check. This could lead to remote code execution with no additional execution privileges needed. User interaction is not needed for exploitation. Patch ID: ALPS06784478; Issue ID: ALPS06784478.
Affected Software
30 affected components
Google Android=10.0
Google Android=11.0
Google Android=12.0
Yoctoproject Yocto=3.1
MediaTek Mt6580
MediaTek Mt6735
MediaTek Mt6737
MediaTek Mt6739
MediaTek Mt6750s
MediaTek Mt6753
MediaTek Mt6755s
MediaTek MT6757
MediaTek Mt6757c
MediaTek Mt6757cd
MediaTek Mt6757ch
MediaTek Mt6763
MediaTek Mt6771
MediaTek Mt8163
MediaTek Mt8167
MediaTek Mt8167s
MediaTek Mt8173
MediaTek Mt8183
MediaTek Mt8321
MediaTek Mt8362a
MediaTek Mt8385
MediaTek Mt8518
MediaTek Mt8532
MediaTek Mt8765
MediaTek Mt8788
Google Android
Event History
Sep 6, 2022
CVE Published
via MITRE·05:19 PM
Data Sourced
via MITRE·05:19 PM
DescriptionWeakness
Jun 5, 2025
Data Sourced
via Android·06:56 PM
SeverityAffected Software
Frequently Asked Questions
1
What is the severity of CVE-2022-26447?
The severity of CVE-2022-26447 is critical with a CVSS score of 9.8.
2
How can CVE-2022-26447 be exploited?
CVE-2022-26447 can be exploited remotely without user interaction, leading to potential remote code execution.
3
Which software products are affected by CVE-2022-26447?
Google Android versions 10.0, 11.0, and 12.0, as well as Yoctoproject Yocto 3.1, are affected by CVE-2022-26447.
4
Is the Mediatek Mt6580 vulnerable to CVE-2022-26447?
No, the Mediatek Mt6580 is not vulnerable to CVE-2022-26447.
5
How can I fix CVE-2022-26447?
To fix CVE-2022-26447, apply the patch ID ALPS06784478 provided by the vendor.