Published April 4, 2022 | Updated April 5, 2022
The Android Security Bulletin contains details of security vulnerabilities
affecting Android devices. Security patch levels of
2022-04-05 or later address all of these issues.
To learn how to check a device's security patch level, see
Check and update your Android version
.
Android partners are notified of all issues at least a month before publication.
Source code patches 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 patches
outside of AOSP.
The most severe of these issues is a high security vulnerability in the
Framework component that could lead to local escalation of privilege 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-04-01 security patch level vulnerability details
In the sections below, we provide details for each of the security
vulnerabilities that apply to the 2022-04-01 patch 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.
The most severe vulnerability in this section could lead to remote
information
disclosure with no additional execution privileges needed.
CVE
|
References
|
Type
|
Severity
|
Updated AOSP versions
|
CVE-2021-39803
|
A-193790350
|
ID
|
High
|
10, 11, 12, 12L
|
CVE-2021-39804
|
A-215002587
|
DoS
|
High
|
11, 12, 12L
|
System
The most severe vulnerability in this section could lead to local escalation
of
privilege with no additional execution privileges needed.
CVE
|
References
|
Type
|
Severity
|
Updated AOSP versions
|
CVE-2021-39808
|
A-209966086
|
EoP
|
High
|
10, 11, 12
|
CVE-2021-39805
|
A-212694559
|
ID
|
High
|
12, 12L
|
CVE-2021-39809
|
A-205837191
|
ID
|
High
|
10, 11, 12, 12L
|
Google Play system updates
The following issues are included in Project Mainline components.
Component
|
CVE
|
MediaProvider
|
CVE-2021-39795
|
Media Codecs
|
CVE-2021-39803
|
2022-04-05 security patch level vulnerability details
In the sections below, we provide details for each of the security
vulnerabilities that apply to the 2022-04-05 patch 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.
System
The most severe vulnerability in this section could lead to local escalation
of
privilege from the Guest account with no additional execution privileges
needed.
CVE
|
References
|
Type
|
Severity
|
Updated AOSP versions
|
CVE-2021-39807
|
A-209446496
|
EoP
|
High
|
10, 11, 12, 12L
|
Kernel components
The most severe vulnerability in this section could lead to local escalation
of
privilege with no additional execution privileges needed.
These vulnerabilities affect MediaTek components and further details are
available directly from MediaTek.
The severity assessment of these issues is provided directly by MediaTek.
CVE
|
References
|
Severity
|
Component
|
CVE-2022-20081
|
A-218242055
M-ALPS06461919
*
|
High
|
A-GPS
|
CVE-2021-25477
|
A-220262213
M-MOLY00684727
*
|
High
|
Modem LTE RRC
|
Qualcomm components
These vulnerabilities affect Qualcomm 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.
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.
CVE
|
References
|
Severity
|
Component
|
CVE-2021-30339
|
A-202025975
*
|
Critical
|
Closed-source component
|
CVE-2021-30341
|
A-202024969
*
|
Critical
|
Closed-source component
|
CVE-2021-30342
|
A-202025860
*
|
Critical
|
Closed-source component
|
CVE-2021-30343
|
A-202025978
*
|
Critical
|
Closed-source component
|
CVE-2021-30347
|
A-202025598
*
|
Critical
|
Closed-source component
|
CVE-2021-35104
|
A-213240044
*
|
Critical
|
Closed-source component
|
CVE-2021-30281
|
A-202025858
*
|
High
|
Closed-source component
|
CVE-2021-30338
|
A-202025859
*
|
High
|
Closed-source component
|
CVE-2021-30340
|
A-202025736
*
|
High
|
Closed-source component
|
CVE-2021-30344
|
A-192612963
*
|
High
|
Closed-source component
|
CVE-2021-30345
|
A-202025737
*
|
High
|
Closed-source component
|
CVE-2021-30346
|
A-202025862
*
|
High
|
Closed-source component
|
CVE-2021-30349
|
A-202025797
*
|
High
|
Closed-source component
|
CVE-2021-30350
|
A-202025979
*
|
High
|
Closed-source component
|
CVE-2021-35070
|
A-202025864
*
|
High
|
Closed-source component
|
CVE-2021-35100
|
A-213240046
*
|
High
|
Closed-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 patch level, see
Check and update your Android version
.
- Security patch levels of 2022-04-01 or later address
all issues associated with the 2022-04-01 security patch
level.
- Security patch levels of 2022-04-05 or later address
all issues associated with the 2022-04-05 security patch
level and all previous patch levels.
Device manufacturers that include these updates should set the patch string
level to:
- [ro.build.version.security_patch]:[2022-04-01]
- [ro.build.version.security_patch]:[2022-04-05]
For some devices on Android 10 or later, the Google Play system update
will have a date string that matches the 2022-04-01
security patch level.
Please see
this article
for more details on how
to install
security updates.
2. Why does this bulletin have two security patch levels?
This bulletin has two security patch 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 patch level.
- Devices that use the 2022-04-01 security patch level
must include all issues associated with that security patch level, as well
as
fixes for all issues reported in previous security bulletins.
- Devices that use the security patch level of 2022-04-05
or newer must include all applicable patches 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.
Abbreviation
|
Definition
|
RCE
|
Remote code execution
|
EoP
|
Elevation of privilege
|
ID
|
Information disclosure
|
DoS
|
Denial of service
|
N/A
|
Classification 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
value belongs.
Prefix
|
Reference
|
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 patch level on Android
devices. Additional security vulnerabilities that are documented in the
device/partner security bulletins are not required for
declaring a security patch 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
Version
|
Date
|
Notes
|
1.0
|
April 4, 2022
|
Bulletin Published
|
1.1
|
April 5, 2022
|
Bulletin revised to include AOSP links
|
2.0
|
July 18, 2022
|
Revised CVE table
|