CVE-2022-20026: High severity Google Android vulnerability

Published Feb 7, 2022

Updated

In Bluetooth, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation. Patch ID: ALPS06126827; Issue ID: ALPS06126827.

Affected Software

12 affected components

Google Android

Google Android=8.1

Google Android=9.0

Google Android=10.0

Google Android=11.0

Google Android=12.0

MediaTek Mt8167

MediaTek Mt8175

MediaTek Mt8183

MediaTek Mt8362a

MediaTek Mt8365

MediaTek Mt8385

Event History

Feb 7, 2022

CVE Published

via Android·12:00 AM

Data Sourced

via Android·12:00 AM

SeverityAffected Software

Feb 9, 2022

CVE Published

via MITRE·10:05 PM

Data Sourced

via MITRE·10:05 PM

DescriptionWeakness

Frequently Asked Questions

What is the severity of CVE-2022-20026?

The severity of CVE-2022-20026 is considered critical, as it allows for local escalation of privilege without any additional execution privileges needed.

How do I fix CVE-2022-20026?

To fix CVE-2022-20026, users should apply the latest security update provided by Google for their Android devices.

Who is affected by CVE-2022-20026?

CVE-2022-20026 affects Android versions 8.1, 9.0, 10.0, 11.0, and 12.0.

Is user interaction needed for exploiting CVE-2022-20026?

No, user interaction is not needed for exploiting CVE-2022-20026.

What types of systems are vulnerable to CVE-2022-20026?

CVE-2022-20026 primarily affects devices running susceptible versions of Google Android.