Android Security Bulletin—August 2022

Published August 1, 2022 | Updated August 17, 2022

The Android Security Bulletin contains details of security vulnerabilities affecting Android devices. Security levels of 2022-08-05 or later address all of these issues. To learn how to check a device's security level, see Check and update your Android version.

Android partners are notified of all issues at least a month before publication. Source code es for these issues have been released to the Android Open Source Project (AOSP) repository and linked from this bulletin. This bulletin also includes links to es outside of AOSP.

The most severe of these issues is a critical security vulnerability in the System component that could lead to remote code execution over Bluetooth with no additional execution privileges needed. The severity assessment is based on the effect that exploiting the vulnerability would possibly have on an affected device, assuming the platform and service mitigations are turned off for development purposes or if successfully bypassed.

Refer to the Android and Google Play Protect mitigations section for details on the Android security platform protections and Google Play Protect, which improve the security of the Android platform.

Android and Google service mitigations

This is a summary of the mitigations provided by the Android security platform and service protections such as Google Play Protect. These capabilities reduce the likelihood that security vulnerabilities could be successfully exploited on Android.

  • Exploitation for many issues on Android is made more difficult by enhancements in newer versions of the Android platform. We encourage all users to update to the latest version of Android where possible.
  • The Android security team actively monitors for abuse through Google Play Protect and warns users about Potentially Harmful Applications. Google Play Protect is enabled by default on devices with Google Mobile Services, and is especially important for users who install apps from outside of Google Play.

2022-08-01 security level vulnerability details

In the sections below, we provide details for each of the security vulnerabilities that apply to the 2022-08-01 level. Vulnerabilities are grouped under the component they affect. Issues are described in the tables below and include CVE ID, associated references, type of vulnerability, severity, and updated AOSP versions (where applicable). When available, we link the public change that addressed the issue to the bug ID, like the AOSP change list. When multiple changes relate to a single bug, additional references are linked to numbers following the bug ID. Devices with Android 10 and later may receive security updates as well as Google Play system updates.

Framework

The most severe vulnerability in this section could lead to local escalation of privilege with no additional execution privileges needed.

CVEReferencesTypeSeverityUpdated AOSP versions
CVE-2021-39696A-185810717 [2]EoPHigh10, 11, 12
CVE-2022-20344A-232541124 [2]EoPHigh10, 11, 12, 12L
CVE-2022-20348A-228315529 [2]EoPHigh10, 11, 12, 12L
CVE-2022-20349A-228315522 [2]EoPHigh10, 11, 12, 12L
CVE-2022-20356A-215003903 [2]EoPHigh11, 12, 12L
CVE-2022-20350A-228178437 [2] [3] [4] [5]IDHigh10, 11, 12, 12L
CVE-2022-20352A-222473855 [2]IDHigh12, 12L
CVE-2022-20357A-214999987 [2]IDHigh12, 12L
CVE-2022-20358A-203229608 [2]IDHigh10, 11, 12, 12L

Media Framework

The most severe vulnerability in this section could lead to remote information disclosure with no additional execution privileges needed.

CVEReferencesTypeSeverityUpdated AOSP versions
CVE-2022-20346A-230493653 [2]IDHigh10, 11, 12, 12L
CVE-2022-20353A-221041256 [2] [3] [4] [5] [6]IDHigh10, 11, 12, 12L

System

The most severe vulnerability in this section could lead to remote code execution over Bluetooth with no additional execution privileges needed.

CVEReferencesTypeSeverityUpdated AOSP versions
CVE-2022-20345A-230494481 [2]RCECritical12, 12L
CVE-2022-20347A-228450811 [2]EoPHigh10, 11, 12, 12L
CVE-2022-20354A-219546241 [2]EoPHigh11, 12, 12L
CVE-2022-20360A-228314987 [2]EoPHigh10, 11, 12, 12L
CVE-2022-20361A-231161832 [2]EoPHigh10, 11, 12, 12L
CVE-2022-20355A-219498290 [2]DoSHigh10, 11, 12, 12L

Google Play system updates

The following issues are included in Project Mainline components.

ComponentCVE
Media Framework componentsCVE-2022-20346

2022-08-05 security level vulnerability details

In the sections below, we provide details for each of the security vulnerabilities that apply to the 2022-08-05 level. Vulnerabilities are grouped under the component they affect. Issues are described in the tables below and include CVE ID, associated references, type of vulnerability, severity, and updated AOSP versions (where applicable). When available, we link the public change that addressed the issue to the bug ID, like the AOSP change list. When multiple changes relate to a single bug, additional references are linked to numbers following the bug ID.

Kernel components

The vulnerability in this section could lead to local escalation of privileges with User execution privileges needed.

CVEReferencesTypeSeverityComponent
CVE-2022-1786A-233078742
Upstream kernel
EoPHighFilesystem (fs)

Imagination Technologies

These vulnerabilities affect Imagination Technologies components and further details are available directly from Imagination Technologies. The severity assessment of these issues is provided directly by Imagination Technologies.

CVEReferencesSeverityComponent
CVE-2021-0698
A-236848165*HighPowerVR-GPU
CVE-2021-0887
A-236848817*HighPowerVR-GPU
CVE-2021-0891A-236849490*HighPowerVR-GPU
CVE-2021-0946
A-236846966*HighPowerVR-GPU
CVE-2021-0947
A-236838960*HighPowerVR-GPU
CVE-2021-39815A-232440670*HighPowerVR-GPU
CVE-2022-20122A-232441339*HighPowerVR-GPU

MediaTek components

This vulnerability affects MediaTek components and further details are available directly from MediaTek. The severity assessment of this issue is provided directly by MediaTek.

CVEReferencesSeverityComponent
CVE-2022-20082A-231271467
M-ALPS07044730*
HighGPU

Unisoc components

This vulnerability affects Unisoc components and further details are available directly from Unisoc. The severity assessment of this issue is provided directly by Unisoc.

CVEReferencesSeverityComponent
CVE-2022-20239A-233972091
U-1883877*
HighVSP

Qualcomm components

This vulnerability affects Qualcomm components and are described in further detail in the appropriate Qualcomm security bulletin or security alert. The severity assessment of this issue is provided directly by Qualcomm.

CVEReferencesSeverityComponent
CVE-2022-22080
A-231156274
QC-CR#2898981
HighAudio

Qualcomm closed-source components

These vulnerabilities affect Qualcomm closed-source components and are described in further detail in the appropriate Qualcomm security bulletin or security alert. The severity assessment of these issues is provided directly by Qualcomm.

CVEReferencesSeverityComponent
CVE-2021-30259A-187074564*HighClosed-source component
CVE-2022-22059A-231156126*HighClosed-source component
CVE-2022-22061A-218338332*HighClosed-source component
CVE-2022-22062
A-218338070*HighClosed-source component
CVE-2022-22067A-218338889*HighClosed-source component
CVE-2022-22069A-218339148*HighClosed-source component
CVE-2022-22070A-218338870*HighClosed-source component
CVE-2022-25668A-231156523*HighClosed-source component

Common questions and answers

This section answers common questions that may occur after reading this bulletin.

1. How do I determine if my device is updated to address these issues?

To learn how to check a device's security level, see Check and update your Android version.

  • Security levels of 2022-08-01 or later address all issues associated with the 2022-08-01 security level.
  • Security levels of 2022-08-05 or later address all issues associated with the 2022-08-05 security level and all previous levels.

Device manufacturers that include these updates should set the string level to:

  • [ro.build.version.security_]:[2022-08-01]
  • [ro.build.version.security_]:[2022-08-05]

For some devices on Android 10 or later, the Google Play system update will have a date string that matches the 2022-08-01 security level. Please see this article for more details on how to install security updates.

2. Why does this bulletin have two security levels?

This bulletin has two security levels so that Android partners have the flexibility to fix a subset of vulnerabilities that are similar across all Android devices more quickly. Android partners are encouraged to fix all issues in this bulletin and use the latest security level.

  • Devices that use the 2022-08-01 security level must include all issues associated with that security level, as well as fixes for all issues reported in previous security bulletins.
  • Devices that use the security level of 2022-08-05 or newer must include all applicable es in this (and previous) security bulletins.

Partners are encouraged to bundle the fixes for all issues they are addressing in a single update.

3. What do the entries in the Type column mean?

Entries in the Type column of the vulnerability details table reference the classification of the security vulnerability.

AbbreviationDefinition
RCERemote code execution
EoPElevation of privilege
IDInformation disclosure
DoSDenial of service
N/AClassification not available

4. What do the entries in the References column mean?

Entries under the References column of the vulnerability details table may contain a prefix identifying the organization to which the reference mvalue belongs.

PrefixReference
A-Android bug ID
QC-Qualcomm reference number
M-MediaTek reference number
N-NVIDIA reference number
B-Broadcom reference number
U-UNISOC reference number

5. What does an * next to the Android bug ID in the References column mean?

Issues that are not publicly available have an * next to the corresponding reference ID. The update for that issue is generally contained in the latest binary drivers for Pixel devices available from the Google Developer site.

6. Why are security vulnerabilities split between this bulletin and device / partner security bulletins, such as the Pixel bulletin?

Security vulnerabilities that are documented in this security bulletin are required to declare the latest security level on Android devices. Additional security vulnerabilities that are documented in the device / partner security bulletins are not required for declaring a security level. Android device and chipset manufacturers may also publish security vulnerability details specific to their products, such as Google, Huawei, LGE, Motorola, Nokia, or Samsung.

Versions

VersionDateNotes
1.0August 1, 2022Bulletin Published
1.1August 3, 2022Bulletin revised to include AOSP links