A use-after-free flaw was found in the Linux kernel’s Bluetooth subsystem in the way user calls connect to the socket and disconnect simultaneously due to a race condition. This flaw allows a user to crash the system or escalate their privileges. The highest threat from this vulnerability is to confidentiality, integrity, as well as system availability.

CVE-2021-3752: [PATCH 5.15 187/917] Bluetooth: fix use-after-free error in lock_sock_nested()

Improper input validation vulnerability in SmartTagPlugin prior to version 1.2.15-6 allows privileged attackers to trigger a XSS on a victim's devices.

This Cookie Policy describes the different types of cookies that may be used in connection with Samsung Mobile Security website which is owned and controlled by Samsung Electronics Co., Ltd (“Samsung Electronics”). This Cookie Policy also describes how you can manage cookies.

It’s important that you check back often for updates to the Policy as we may change it from time to time to reflect changes to our use of cookies. Please check the date at the top of this page to see when this Policy was last revised. Any changes to this Policy will become effective when we make the revised Policy available on our website.

Samsung Electronics has offices across Europe, so we can ensure that your request or query will be handled by the data protection team based in your region. If you have any questions, the easiest way to contact us is through our Privacy Support Page at https://www.samsung.com/request-desk.

You can also contact us at:

European Data Protection Officer  
Samsung Electronics (UK) Limited  
Samsung House, 2000 Hillswood Drive, Chertsey, Surrey KT16 0RS

**Cookies**

Cookies are small files that store information on your computer, TV, mobile phone, or other device. They enable the entity that put the cookie on your device to recognize you across different websites, services, devices, and/or browsing sessions.

We use the following types of cookies on this website:

**Essential Cookies**: enable you to receive the services you request via our website. Without these cookies, services that you have asked for cannot be provided. For example, these enable to identify users and provide proper service for each user. These cookies are automatically enabled and cannot be turned off because they are essential to enable you to browse our website. Without these cookies this Samsung Mobile Security website could not be provided.

Cookie

Domain

Purpose

JSESSIONID

security.samsungmobile.com

to keep login session

lastActivityTime

security.samsungmobile.com

to save the user's last activity time to automatically logout after 30 minutes of inactivity

**Managing Cookies and Other Technologies**

You can also update your browser settings at any time, if you want to remove or block cookies from your device (consult your browser's "help" menu to learn how to remove or block cookies). Samsung Electronics is not responsible for your browser settings. You can find good and simple instructions on how to manage cookies on the different types of web browsers at http://www.allaboutcookies.org.

CVE-2022-24926: Samsung Mobile Security

An Improper access control vulnerability in StBedtimeModeReceiver in Wear OS 3.0 prior to Firmware update Feb-2022 Release allows untrusted applications to change bedtime mode without a proper permission.

CVE-2022-23994: Samsung Mobile Security

ismsEx service is a vendor service in unisoc equipment?ismsEx service is an extension of sms system service?but it does not check the permissions of the caller?resulting in permission leaks?Third-party apps can use this service to arbitrarily modify and set system properties?Product: AndroidVersions: Android SoCAndroid ID: A-207479207

_Published February 7, 2022 | Updated February 17, 2022_

The Android Security Bulletin contains details of security vulnerabilities affecting Android devices. Security patch levels of 2022-02-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 critical security vulnerability in the System component that could lead to remote 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-02-01 security patch level vulnerability details**

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

    

CVE

References

Type

Severity

Updated AOSP versions

CVE-2021-39619

A-197399948

EoP

High

11, 12

CVE-2021-39663

A-200682135\*

EoP

High

10

CVE-2021-39676

A-197228210\*

EoP

High

11

CVE-2021-39664

A-203938029

ID

High

12

**Media Framework**

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-2020-13112

A-194342672\*

EoP

High

10, 11

CVE-2020-13113

A-196085005\*

EoP

High

10, 11

CVE-2021-39665

A-204077881

ID

High

12

CVE-2021-39666

A-204445255 \[2\]

ID

High

11, 12

**System**

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

    

CVE

References

Type

Severity

Updated AOSP versions

CVE-2021-39675

A-205729183

EoP

Critical

12

CVE-2021-39668

A-193445603

EoP

High

11, 12

CVE-2021-39669

A-196969991

EoP

High

11, 12

CVE-2021-39671

A-206718630 \[2\]

EoP

High

12

CVE-2021-39674

A-201083442

EoP

High

10, 11, 12

CVE-2021-0706

A-193444889\*

DoS

High

10, 11

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

In the sections below, we provide details for each of the security vulnerabilities that apply to the 2022-02-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 vulnerability in this section could lead to local information disclosure with no additional execution privileges needed.

    

CVE

References

Type

Severity

Updated AOSP versions

CVE-2021-39631

A-193890833 \[2\]

ID

High

10, 11, 12

**Amlogic components**

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

   

CVE

References

Severity

Component

CVE-2021-39672  

A-202018701\*

High

Fastboot

**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-2022-20024  

A-209705228  
M-ALPS06219064\*

High

System service

CVE-2022-20025

A-209700749  
M-ALPS06126832\*

High

Bluetooth

CVE-2022-20026

A-209705229  
M-ALPS06126827\*

High

Bluetooth

CVE-2022-20027

A-209702508  
M-ALPS06126826\*

High

Bluetooth

CVE-2022-20028

A-209702509  
M-ALPS06198663\*

High

Bluetooth

**Unisoc components**

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

   

CVE

References

Severity

Component

CVE-2021-39616

A-204686438  
U-1704529\*

High

sprd-vowifi

CVE-2021-39635

A-206492634  
U-1731024\*

High

ims\_ex

CVE-2021-39658

A-207479207  
U-1732729\*

High

IsmsEx

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

A-202025798  
QC-CR#2982971

High

Bluetooth

CVE-2021-35069  

A-203032261  
QC-CR#3001191

High

WLAN

CVE-2021-35074

A-204905255  
QC-CR#2998013

High

Kernel

CVE-2021-35075  

A-204905325  
QC-CR#2998149

High

Kernel

CVE-2021-35077

A-204904989  
QC-CR#3007135

High

Kernel

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

A-195750667\*

Critical

Closed-source component

CVE-2021-30309

A-195750718\*

High

Closed-source component

CVE-2021-30318

A-202025316\*

High

Closed-source component

CVE-2021-30322

A-195751178\*

High

Closed-source component

CVE-2021-30323

A-195750446\*

High

Closed-source component

CVE-2021-30326

A-195751080\*

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

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

February 7, 2022

Bulletin Released

1.1

February 8, 2022

Bulletin revised to include AOSP links

1.2

February 17, 2022

Revised CVE table

CVE-2021-39658: Android Security Bulletin—February 2022  |  Android Open Source Project

Improper authorization vulnerability in Galaxy Store prior to 4.5.36.5 allows remote app installation of the allowlist.

CVE-2022-22288: Samsung Mobile Security

Improper authorization in TelephonyManager prior to SMR Jan-2022 Release 1 allows attackers to get IMSI without READ_PRIVILEGED_PHONE_STATE permission

CVE-2022-22272: Samsung Mobile Security

In createFromParcel of OutputConfiguration.java, there is a possible parcel serialization/deserialization mismatch due to improper input validation. 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-11 Android-9Android ID: A-188675581

_Published November 1, 2021 | Updated December 3, 2021_

The Android Security Bulletin contains details of security vulnerabilities affecting Android devices. Security patch levels of 2021-11-06 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 critical security vulnerability in the System component that could enable a remote attacker using a specially crafted transmission to execute arbitrary code within the context of a privileged process. 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.

**2021-11-01 security patch level vulnerability details**

In the sections below, we provide details for each of the security vulnerabilities that apply to the 2021-11-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 attacker to gain access to additional permissions with no user interaction required.

    

CVE

References

Type

Severity

Updated AOSP versions

CVE-2021-0799

A-197647956

EoP

High

12

CVE-2021-0921

A-195962697

EoP

High

11

CVE-2021-0923

A-195338390

EoP

High

12

CVE-2021-0926

A-191053931

EoP

High

9, 10, 11, 12

CVE-2021-0933

A-172251622

EoP

High

9, 10, 11, 12

CVE-2020-13871

A-192606047

ID

High

11

CVE-2021-0653

A-177931370

ID

High

9, 10, 11

CVE-2021-0922

A-195630721

EoP

Moderate

11

**Media 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-0928

A-188675581

EoP

High

9, 10, 11

CVE-2021-0650

A-190286685

ID

High

9, 10, 11

**System**

The most severe vulnerability in this section could enable a remote attacker using a specially crafted transmission to execute arbitrary code within the context of a privileged process.

    

CVE

References

Type

Severity

Updated AOSP versions

CVE-2021-0918

A-197536150

RCE

Critical

12

CVE-2021-0930

A-181660091

RCE

Critical

9, 10, 11, 12

CVE-2021-0434

A-167403112 \[2\] \[3\] \[4\] \[5\] \[6\]

EoP

High

9, 10, 11

CVE-2021-0649

A-191382886 \[2\]

EoP

High

11

CVE-2021-0932

A-173025705

EoP

High

10

CVE-2021-0925

A-191444150

ID

High

12

CVE-2021-0931

A-180747689

ID

High

9, 10, 11, 12

CVE-2021-0919

A-197336441

DoS

Moderate

9, 10, 11

**Google Play system updates**

The following issues are included in Project Mainline components.

 

Component

CVE

Tethering

CVE-2021-0653

Media Framework components

CVE-2021-0650

Tethering

CVE-2021-0649

**2021-11-05 security patch level vulnerability details**

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

**Kernel components**

The most severe vulnerability in this section could result in local escalation of privilege due to a use after free.

    

CVE

References

Type

Severity

Component

CVE-2021-0920

A-196926917  
Upstream kernel

EoP

High

Kernel

CVE-2021-0924

A-194461020  
Upstream kernel

EoP

High

USB

CVE-2021-0929

A-187527909  
Upstream kernel \[2\] \[3\]

EoP

High

ION

**Android TV**

The most severe vulnerability in this section could enable a proximate attacker to silently pair with a TV and execute arbitrary code with no privileges or user interaction required.

    

CVE

References

Type

Severity

Component

CVE-2021-0889

A-180745296

RCE

Critical

Android TV Remote Service

CVE-2021-0927

A-189824175

EoP

High

TvInputManager

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

    

CVE

References

Severity

Component

CVE-2021-0672  

A-199678035  
M-ALPS05969704 \*

High

Browser app

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

A-187074639 \*

Critical

Closed-source component

CVE-2021-1975  

A-187074053 \*

Critical

Closed-source component

CVE-2021-1921  

A-187074562 \*

High

Closed-source component

CVE-2021-1973  

A-187074563 \*

High

Closed-source component

CVE-2021-1979  

A-187073200 \*

High

Closed-source component

CVE-2021-1981  

A-187074764 \*

High

Closed-source component

CVE-2021-1982  

A-187074484 \*

High

Closed-source component

CVE-2021-30254  

A-187074014 \*

High

Closed-source component

CVE-2021-30255  

A-187074054 \*

High

Closed-source component

CVE-2021-30284  

A-187074013 \*

High

Closed-source component

**2021-11-06 security patch level vulnerability details**

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

**Kernel components**

The vulnerability in this section could lead to a local escalation of privilege due to a use after free.

    

CVE

References

Type

Severity

Component

CVE-2021-1048

A-204573007  
Upstream kernel

EoP

High

Kernel

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

For some devices on Android 10 or later, the Google Play system update will have a date string that matches the 2021-11-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 2021-11-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 2021-11-05 or newer must include all applicable patches in this (and previous) security bulletins.
*   Devices that use the security patch level of 2021-11-06 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

November 1, 2021

Bulletin Released

1.1

November 2, 2021

Bulletin revised to include AOSP links

1.2

December 3, 2021

Revised CVE table

CVE-2021-0928: Android Security Bulletin—November 2021

Intent redirection vulnerability in Samsung Blockchain Wallet prior to version 1.3.02.8 allows attacker to execute privileged action.

CVE-2021-25526

Improper authorization vulnerability in Samsung Flow mobile application prior to 4.8.03.5 allows Samsung Flow PC application connected with user device to access part of notification data in Secure Folder without authorization.

CVE-2021-25507

check_smart before 6.9.1 allows unintended drive access by an unprivileged user because it only checks for a substring match of a device path (the /dev/bus substring and a number), aka an unanchored regular expression.

Tag

#samsung