NVIDIA Linux kernel distributions contain a vulnerability in nvmap NVGPU_IOCTL_CHANNEL_SET_ERROR_NOTIFIER, where improper access control may lead to code execution, compromised integrity, or denial of service.

**Details**

This section summarizes the potential impact that this security update addresses. Descriptions use CWE™, and base scores and vectors use CVSS V3.1 standards.

**CVE ID**

**Description**

**Base Score**

**Vector**

CVE‑2021‑1106

NVIDIA Linux kernel distributions contain a vulnerability in `nvmap`, where writes may be allowed to read-only buffers, which may result in escalation of privileges, denial of service, information disclosure, or data tampering.

7.8

AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

CVE‑2021‑1107

NVIDIA Linux kernel distributions contain a vulnerability in `nvmap` `NVMAP_IOC_WRITE*` paths, where improper access controls may lead to code execution, denial of service, or compromised integrity of system components.

7.8

AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

CVE‑2021‑34401

NVIDIA Linux kernel distributions contain a vulnerability in `nvmap` `NVGPU_IOCTL_CHANNEL_SET_ERROR_NOTIFIER`, where improper access control may lead to code execution, compromised integrity, or denial of service.

7.8

AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

CVE‑2021‑1108

NVIDIA Linux kernel distributions contain a vulnerability in FuSa Capture (VI/ISP), where integer underflow caused by lack of input validation may lead to complete denial of service, partial integrity, and serious confidentiality loss for all processes in the system.

7.3

AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:H

CVE‑2021‑34402

NVIDIA Tegra kernel driver contains a vulnerability in NVIDIA NVDEC, where a user with high privileges might be able to read from or write to a memory location that is outside the intended boundary of the buffer, which may lead to denial of service, Information disclosure, loss of Integrity, or possible escalation of privileges.

6.7

AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H

CVE‑2021‑34403

NVIDIA Linux distributions contain a vulnerability in nvmap ioctl, which allows any user with a local account to exploit a use-after-free condition, leading to code privilege escalation, loss of confidentiality and integrity, or denial of service.

7.8

AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

CVE‑2021‑34404

Android images for T210 provided by NVIDIA contain a vulnerability in BROM, where failure to limit access to AHB-DMA when BROM fails may allow an unprivileged attacker with physical access to cause denial of service or impact integrity and confidentiality beyond the security scope of BROM.

7.1

AV:P/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H

CVE‑2021‑34405

NVIDIA Linux distributions contain a vulnerability in TrustZone’s `TEE_Malloc` function, where an unchecked return value causing a null pointer dereference may lead to denial of service.

5.5

AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

CVE‑2021‑1112

NVIDIA Linux kernel distributions contain a vulnerability in `nvmap`, where a null pointer dereference may lead to denial of service.

5.5

AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

CVE‑2021‑34406

NVIDIA Tegra kernel driver contains a vulnerability in NVHost, where a specific race condition can lead to a null pointer dereference, which may lead to a system reboot.

4.7

AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H

SHIELD TV update includes Android™ Security Patch level **2021-09-05**. For more information about what is included in Android security patch levels, refer to the Android Security Bulletins.

The NVIDIA risk assessment is based on an average of risk across a diverse set of installed systems and may not represent the true risk to your local installation. NVIDIA recommends evaluating the risk to your specific configuration.

**Security Updates**

The following table lists the NVIDIA software products affected, versions affected, and the updated version that includes this security update. Download the update through Settings\>About\>System update.

**Software Product**

**Operating System**

**Affected Versions**

**Updated Version**

SHIELD TV

Android-P

Shield Experience prior to SE 9.0

Shield Experience Upgrade SE 9.0

**Note:**

*   Earlier releases of this product are also affected. If you are using an earlier release, upgrade to the latest release.

**Mitigations**

See Security Updates for the version to install.

**Acknowledgements**

CVE‑2021‑34406: NVIDIA thanks Billy Laws for reporting this issue.

**Get the Most Up to Date Product Security Information**

Visit the NVIDIA Product Security page to

*   Subscribe to security bulletin notifications
*   See the current list of NVIDIA security bulletins
*   Report a potential security issue in any NVIDIA supported product
*   Learn more about the vulnerability management process followed by the NVIDIA Product Security Incident Response Team (PSIRT)

**Revision History**

  

**Revision**

**Date**

**Description**

1.0

January 12, 2022

Initial release

**Support**

If you have any questions about this Security Bulletin, contact NVIDIA Support.

**Disclaimer**

ALL NVIDIA INFORMATION, DESIGN SPECIFICATIONS, REFERENCE BOARDS, FILES, DRAWINGS, DIAGNOSTICS, LISTS, AND OTHER DOCUMENTS (TOGETHER AND SEPARATELY, “MATERIALS”) ARE BEING PROVIDED “AS IS.” NVIDIA MAKES NO WARRANTIES, EXPRESS, IMPLIED, STATUTORY, OR OTHERWISE WITH RESPECT TO THE MATERIALS, AND ALL EXPRESS OR IMPLIED CONDITIONS, REPRESENTATIONS AND WARRANTIES, INCLUDING ANY IMPLIED WARRANTY OR CONDITION OF TITLE, MERCHANTABILITY, SATISFACTORY QUALITY, FITNESS FOR A PARTICULAR PURPOSE AND NON-INFRINGEMENT, ARE HEREBY EXCLUDED TO THE MAXIMUM EXTENT PERMITTED BY LAW.

Information is believed to be accurate and reliable at the time it is furnished. However, NVIDIA Corporation assumes no responsibility for the consequences of use of such information or for any infringement of patents or other rights of third parties that may result from its use. No license is granted by implication or otherwise under any patent or patent rights of NVIDIA Corporation. Specifications mentioned in this publication are subject to change without notice. This publication supersedes and replaces all information previously supplied. NVIDIA Corporation products are not authorized for use as critical components in life support devices or systems without express written approval of NVIDIA Corporation.

CVE-2021-34401: Security Bulletin: NVIDIA SHIELD TV - January 2022

There is a NULL pointer deference in the Allwinner R818 SoC Android Q SDK V1.0 camera driver /dev/cedar_dev that could use the ioctl cmd IOCTL_GET_IOMMU_ADDR to cause a system crash.

CVE-2021-38785

There is a NULL pointer dereference in the syscall open_exec function of Allwinner R818 SoC Android Q SDK V1.0 that could executable a malicious file to cause a system crash.

CVE-2021-38784

There is a Out-of-Bound Write in the Allwinner R818 SoC Android Q SDK V1.0 camera driver "/dev/cedar_dev" through iotcl cmd IOCTL_SET_PROC_INFO and IOCTL_COPY_PROC_INFO, which could cause a system crash or EoP.

© 2020 WANGAN.COM 帮助网安从业者成长；关注产业发展，做网络安全忠诚卫士！

关于我们用户协议隐私政策赞助捐赠

CVE-2021-38783: undefined_undefined-网安漏洞平台

Jimoty App for Android versions prior to 3.7.42 uses a hard-coded API key for an external service. By exploiting this vulnerability, API key for an external service may be obtained by analyzing data in the app.

Published:2022/01/12  Last Updated:2022/01/12

**Overview**

Jimoty App for Android uses a hard-coded API key for an external service.

**Products Affected**

*   Jimoty App for Android versions prior to 3.7.42

**Description**

Jimoty App for Android provided by Jimoty, Inc. uses a hard-coded API key for an external service (CWE-798).

**Impact**

API key for an external service may be obtained by analyzing data in the app.  
Note that a user is not directly affected by this vulnerability.

**Solution**

**Update the Application**  
Update the application to the latest version according to the information provided by the developer.

According to the developer, the latest app does not hard-code the API key.  
The vulnerable API key has been deactivated, therefore information contained in the vulnerable app can not be abused.

**Vendor Status**

Vendor

Status

Last Update

Vendor Notes

Jimoty, Inc.

Vulnerable

2022/01/12

**References**

**JPCERT/CC Addendum**

**Vulnerability Analysis by JPCERT/CC**

CVSS v3 CVSS:3.0/AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Attack Vector(AV)

Physical (P)

Local (L)

Adjacent (A)

Network (N)

Attack Complexity(AC)

High (H)

Low (L)

Privileges Required(PR)

High (H)

Low (L)

None (N)

User Interaction(UI)

Required (R)

None (N)

Scope(S)

Unchanged (U)

Changed (C)

Confidentiality Impact(C)

None (N)

Low (L)

High (H)

Integrity Impact(I)

None (N)

Low (L)

High (H)

Availability Impact(A)

None (N)

Low (L)

High (H)

CVSS v2 AV:L/AC:L/Au:N/C:P/I:N/A:N

Access Vector(AV)

Local (L)

Adjacent Network (A)

Network (N)

Access Complexity(AC)

High (H)

Medium (M)

Low (L)

Authentication(Au)

Multiple (M)

Single (S)

None (N)

Confidentiality Impact(C)

None (N)

Partial (P)

Complete (C)

Integrity Impact(I)

None (N)

Partial (P)

Complete (C)

Availability Impact(A)

None (N)

Partial (P)

Complete (C)

**Credit**

Masashi Yamane of LAC Co., Ltd. reported this vulnerability to IPA.  
JPCERT/CC coordinated with the developer under Information Security Early Warning Partnership.

**Other Information**

CVE-2022-0131: Jimoty App for Android uses a hard-coded API key for an external service

In ipcSetDataReference of Parcel.cpp, there is a possible way to corrupt memory due to a use after free. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.Product: AndroidVersions: Android-11 Android-12Android ID: A-203847542

_Published January 4, 2022 | January 10, 2022_

The Android Security Bulletin contains details of security vulnerabilities affecting Android devices. Security patch levels of 2022-01-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 will be released to the Android Open Source Project (AOSP) repository in the next 48 hours. We will revise this bulletin with the AOSP links when they are available.

The most severe of these issues is a high security vulnerability in the Android runtime component that could enable a local attacker to bypass memory restrictions in order to gain access to additional permissions. 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-01-01 security patch level vulnerability details**

In the sections below, we provide details for each of the security vulnerabilities that apply to the 2022-01-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 enable a local malicious application to bypass user interaction requirements in order to gain access to additional permissions.

    

CVE

References

Type

Severity

Updated AOSP versions

CVE-2021-39630

A-202768292

EoP

High

12

CVE-2021-39632

A-202159709

EoP

High

11, 12

CVE-2020-0338

A-123700107

ID

High

9, 10

**Media Framework**

The vulnerability in this section could lead to remote escalation of privilege with no additional execution privileges or user interaction needed.

    

CVE

References

Type

Severity

Updated AOSP versions

CVE-2021-39623

A-194105348

EoP

High

9, 10, 11, 12

**System**

The most severe vulnerability in this section could enable a local privileged attacker to install existing packages without requiring user consent.

    

CVE

References

Type

Severity

Updated AOSP versions

CVE-2021-39618

A-196855999

EoP

High

9, 10, 11, 12

CVE-2021-39620

A-203847542

EoP

High

11, 12

CVE-2021-39621

A-185126319

EoP

High

9, 10, 11, 12

CVE-2021-39622

A-192663648

EoP

High

10, 11, 12

CVE-2021-39625

A-194695347

EoP

High

9, 10, 11, 12

CVE-2021-39626

A-194695497

EoP

High

9, 10, 11, 12

CVE-2021-39627

A-185126549

EoP

High

9, 10, 11, 12

CVE-2021-39629

A-197353344

EoP

High

9, 10, 11, 12

CVE-2021-0643

A-183612370

ID

High

10, 11, 12

CVE-2021-39628

A-189575031

ID

High

10, 11

CVE-2021-39659

A-208267659

DoS

High

10, 11, 12

**Google Play system updates**

There are no security issues addressed in Google Play system updates (Project Mainline) this month.

**2022-01-05 security patch level vulnerability details**

In the sections below, we provide details for each of the security vulnerabilities that apply to the 2022-01-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.

**Android runtime**

The vulnerability in this section could enable a local attacker to bypass memory restrictions in order to gain access to additional permissions.

    

CVE

References

Type

Severity

Updated AOSP versions

CVE-2021-0959

A-200284993

EoP

High

12

**Kernel components**

The most severe vulnerability in this section could lead to a local escalation of privilege due to a race condition, with no additional execution privileges or user interaction needed.

    

CVE

References

Type

Severity

Component

CVE-2021-39634

A-204450605  
Upstream kernel

EoP

High

Kernel

CVE-2021-39633

A-150694665  
Upstream kernel

ID

High

Kernel

**Kernel LTS**

The following kernel versions have been updated.

References

Android Launch Version

Kernel Launch Version

Minimum Launch Version

A-182179492

11

5.4

5.4.86

**MediaTek components**

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-2021-31345

A-207693368  
M- MOLY00756840 \*

High

Modem (Nucleus NET TCP/IP)

CVE-2021-31346

A-207646334  
M-MOLY00756840 \*

High

Modem (Nucleus NET TCP/IP)

CVE-2021-31890

A-207646336  
M-MOLY00756840 \*

High

Modem (Nucleus NET TCP/IP)

CVE-2021-40148

A-204728248  
M-MOLY00716585 \*

High

Modem EMM

CVE-2021-31889

A-207646335  
M-MOLY00756840 \*

High

Modem (Nucleus NET TCP/IP)

**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.

   

CVE

References

Severity

Component

CVE-2021-1049

A-204256722  
U-1733219 \*

High

slogmodem

**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.

   

CVE

References

Severity

Component

CVE-2021-30319

A-202025735  
QC-CR#2960714

High

WLAN

CVE-2021-30353

A-202025599  
QC-CR#2993069 \[2\]

High

Audio

**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-30285

A-193070555 \*

Critical

Closed-source component

CVE-2021-30287

A-193070556 \*

High

Closed-source component

CVE-2021-30300

A-193071116 \*

High

Closed-source component

CVE-2021-30301

A-193070342 \*

High

Closed-source component

CVE-2021-30307

A-193070700 \*

High

Closed-source component

CVE-2021-30308

A-193070594 \*

High

Closed-source component

CVE-2021-30311

A-193070557 \*

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-01-01 or later address all issues associated with the 2022-01-01 security patch level.
*   Security patch levels of 2022-01-05 or later address all issues associated with the 2022-01-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-01-01\]
*   \[ro.build.version.security\_patch\]:\[2022-01-05\]

For some devices on Android 10 or later, the Google Play system update will have a date string that matches the 2022-01-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-01-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-01-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

January 4, 2022

Bulletin Released

2.0

January 10, 2022

Revised CVE table

CVE-2021-39620: Android Security Bulletin—January 2022  |  Android Open Source Project

In setLaunchIntent of BluetoothDevicePickerPreferenceController.java, there is a possible way to invoke an arbitrary broadcast receiver due to a confused deputy. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.Product: AndroidVersions: Android-10 Android-12Android ID: A-195668284

_Published January 4, 2022_

The Android Automotive OS (AAOS) Update Bulletin contains details of security vulnerabilities affecting the Android Automotive OS platform. The full AAOS update comprises the security patch level of 2022-01-05 or later from the January 2022 Android Security Bulletin in addition to all issues in this bulletin.

We encourage all customers to accept these updates to their devices.

The most severe of these issues is a high security vulnerability in the AAOS component that could enable a local malicious application to gain access to additional privileges due to a confused deputy. 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.

****Announcements****

*   In addition to the security vulnerabilities described in the January 2022 Android Security Bulletin, the January 2022 Android Automotive OS Update Bulletin also contains patches specifically for AAOS vulnerabilities as described below.

****2022-01-01 security patch level vulnerability details****

In the sections below, we provide details for each of the security vulnerabilities that apply to the 2022-01-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.

****AAOS****

The most severe vulnerability in this section could enable a local malicious application to gain access to additional privileges due to a confused deputy.

    

CVE

References

Type

Severity

Updated AOSP versions

CVE-2021-1035

A-195668284

EoP

High

10, 12

CVE-2021-1036

A-182812255

EoP

High

9, 10, 11, 12

CVE-2021-1037

A-162951906

ID

High

9, 10, 11, 12

****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, read the instructions on the Google device update schedule.

*   Security patch levels of 2022-01-01 or later address all issues associated with the 2022-01-01 security patch level.

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

*   \[ro.build.version.security\_patch\]:\[2022-01-01\]

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

**2\. 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

**3\. 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

**4\. 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.

**5\. 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

January 4, 2022

Bulletin Released

CVE-2021-1035: Android Automotive OS Update Bulletin—January 2022  |  Android Open Source Project

In copy_from_mbox of sss_ice_util.c, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalation of privilege with System execution privileges needed. User interaction is not needed for exploitation.Product: AndroidVersions: Android kernelAndroid ID: A-202003354References: N/A

_Published January 4, 2022_

The Pixel Update Bulletin contains details of security vulnerabilities and functional improvements affecting supported Pixel devices (Google devices). For Google devices, security patch levels of 2022-01-05 or later address all issues in this bulletin and all issues in the January 2022 Android Security Bulletin. To learn how to check a device's security patch level, see Check and update your Android version.

All supported Google devices will receive an update to the 2022-01-05 patch level. We encourage all customers to accept these updates to their devices.

****Announcements****

*   In addition to the security vulnerabilities described in the January 2022 Android Security Bulletin, Google devices also contain patches for the security vulnerabilities described below.

****Security patches****

Vulnerabilities are grouped under the component that they affect. There is a description of the issue and a table with the CVE, associated references, type of vulnerability, severity, and updated Android Open Source Project (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.

****Pixel****

    

CVE

References

Type

Severity

Component

CVE-2021-39678

A-171742549 \*

EoP

High

Gboard

CVE-2021-39679

A-188745089 \*

EoP

High

Display/graphics

CVE-2021-39682

A-201677538 \*

EoP

High

Display/graphics

CVE-2021-39683

A-202003354 \*

EoP

High

Titan M2

CVE-2021-39684

A-203250788 \*

EoP

High

Bootloader

CVE-2021-40490

A-199579676 \*

EoP

High

Kernel

CVE-2021-39680

A-197965864 \*

ID

High

Titan M2

CVE-2021-39681

A-200251074 \*

EoP

Moderate

Telephony

****Qualcomm components****

    

CVE

References

Severity

Component

CVE-2021-30313

A-178720043

QC-CR#2878995

Moderate

Kernel

****Qualcomm closed-source components****

    

CVE

References

Severity

Component

CVE-2021-30314

A-193072178 \*

Moderate

Closed-source component

****Functional patches****

For details on the new bug fixes and functional patches included in this release, refer to the Pixel Community forum.

****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?**

Security patch levels of 2022-01-05 or later address all issues associated with the 2022-01-05 security patch level and all previous patch levels. To learn how to check a device's security patch level, read the instructions on the Google device update schedule.

**2\. 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

**3\. 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

**4\. 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 Android bug ID in the _References_ column. The update for that issue is generally contained in the latest binary drivers for Pixel devices available from the Google Developer site.

**5\. Why are security vulnerabilities split between this bulletin and the Android Security Bulletins?**

Security vulnerabilities that are documented in the Android Security Bulletins are required to declare the latest security patch level on Android devices. Additional security vulnerabilities, such as those documented in this bulletin are not required for declaring a security patch level.

****Versions****

  

Version

Date

Notes

1.0

January 4, 2022

Bulletin Released

CVE-2021-39683: Pixel Update Bulletin—January 2022  |  Android Open Source Project

livehelperchat is vulnerable to Cross-Site Request Forgery (CSRF)

CVE-2022-0226: Cross-Site Request Forgery (CSRF) in livehelperchat

Improper validation of function pointer type with actual function signature can lead to assertion in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Voice & Music, Snapdragon Wearables

Tag

#android