|13.0.0 (TQ1A.230105.002, Jan 2023)||Flash||Link||34d676ff4d260f02d9ada1f16f24fd7995c9b9ca832410099950d9c510db8793|
|13.0.0 (TQ1A.230105.002.A1, Jan 2023, Telstra)||Flash||Link||6632344c9647b04bfce622b0decf3733dfb3bc5c3b2c068ea118f8631c1b39b8|
Android Security Bulletin—January 2023bookmark_border
Published January 3, 2022
The Android Security Bulletin contains details of security vulnerabilities affecting Android devices. Security patch levels of 2023-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 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.
Note: Information on the latest over-the-air update (OTA) and firmware images for Google devices is available in the January 2023 Pixel Update Bulletin.
Android and Google service mitigationsThis 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.
2023-01-01 security patch level vulnerability detailsIn the sections below, we provide details for each of the security vulnerabilities that apply to the 2023-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.
FrameworkThe 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-2022-20456 A-242703780 EoP High 10, 11, 12, 12L, 13 CVE-2022-20489 A-242703460 EoP High 10, 11, 12, 12L, 13 CVE-2022-20490 A-242703505 EoP High 10, 11, 12, 12L, 13 CVE-2022-20492 A-242704043 EoP High 10, 11, 12, 12L, 13 CVE-2022-20493 A-242846316 EoP High 10, 11, 12, 12L, 13 CVE-2023-20912 A-246301995 EoP High 13 CVE-2023-20916 A-229256049 EoP High 12, 12L CVE-2023-20918 A-243794108 EoP High 10, 11, 12, 12L, 13 CVE-2023-20919 A-252663068 EoP High 13 CVE-2023-20920 A-204584366 EoP High 10, 11, 12, 12L, 13 CVE-2023-20921 A-243378132 EoP High 10, 11, 12, 12L, 13 CVE-2022-20494 A-243794204 DoS High 10, 11, 12, 12L, 13 CVE-2023-20908 A-239415861 DoS High 10, 11, 12, 12L, 13 CVE-2023-20922 A-237291548 DoS High 11, 12, 12L, 13
SystemThe most severe vulnerability in this section could lead to local escalation of privilege of BLE with no additional execution privileges needed.
CVE References Type Severity Updated AOSP versions CVE-2022-20461 A-228602963 EoP High 10, 11, 12, 12L, 13 CVE-2023-20904 A-246300272 EoP High 12L, 13 CVE-2023-20905 A-241387741 EoP High 10 CVE-2023-20913 A-246933785 EoP High 10, 11, 12, 12L, 13 CVE-2023-20915 A-246930197 EoP High 10, 11, 12, 12L, 13
Google Play system updatesThe following issues are included in Project Mainline components.
Subcomponent CVE MediaProvider CVE-2023-20912
2023-01-05 security patch level vulnerability detailsIn the sections below, we provide details for each of the security vulnerabilities that apply to the 2023-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.
KernelThe most severe vulnerability in this section could lead to remote code execution with no additional execution privileges needed.
CVE References Type Severity Subcomponent CVE-2022-42719 A-253642087
Upstream kernel             
RCE Critical mac80211 CVE-2022-42720 A-253642015
Upstream kernel             
RCE Critical WLAN CVE-2022-42721 A-253642088
Upstream kernel             
RCE Critical Multiple Modules CVE-2022-2959 A-244395411
EoP High Pipe
Kernel componentsThe most severe vulnerability in this section could lead to remote code execution with no additional execution privileges needed.
CVE References Type Severity Subcomponent CVE-2022-41674 A-253641805
Upstream kernel             
RCE Critical WLAN CVE-2023-20928 A-254837884
EoP High Binder driver
Kernel LTSThe following kernel versions have been updated. Kernel version updates are dependent on the version of Android OS at the time of device launch.
References Android Launch Version Kernel Launch Version Minimum Launch Version A-224575820 12 5.10 5.10.101
Imagination TechnologiesThis vulnerability affects Imagination Technologies components and further details are available directly from Imagination Technologies. The severity assessment of this issue is provided directly by Imagination Technologies.
CVE References Severity Subcomponent CVE-2022-20235 A-259967780 * High PowerVR-GPU
MediaTek componentsThese 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 Subcomponent CVE-2022-32635 A-257714327
High gps CVE-2022-32636 A-257846591
High keyinstall CVE-2022-32637 A-257860658
High hevc decoder
Unisoc componentsThese 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 Subcomponent CVE-2022-44425 A-258731891
High Kernel CVE-2022-44426 A-258728978
High Kernel CVE-2022-44427 A-258736883
High Kernel CVE-2022-44428 A-258741356
High Kernel CVE-2022-44429 A-258743555
High Kernel CVE-2022-44430 A-258749708
High Kernel CVE-2022-44431 A-258741360
High Kernel CVE-2022-44432 A-258743558
High Kernel CVE-2022-44434 A-258760518
High Android CVE-2022-44435 A-258759189
High Android CVE-2022-44436 A-258760519
High Android CVE-2022-44437 A-258759192
High Android CVE-2022-44438 A-258760781
Qualcomm componentsThese 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 Subcomponent CVE-2022-22088 A-231156521
Critical Bluetooth CVE-2022-33255 A-250627529
Qualcomm closed-source componentsThese 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 Subcomponent CVE-2021-35097 A-209469821 * Critical Closed-source component CVE-2021-35113 A-209469998 * Critical Closed-source component CVE-2021-35134 A-213239776 * Critical Closed-source component CVE-2022-23960 A-238203772 * High Closed-source component CVE-2022-25725 A-238101314 * High Closed-source component CVE-2022-25746 A-238106983 * High Closed-source component CVE-2022-33252 A-250627159 * High Closed-source component CVE-2022-33253 A-250627591 * High Closed-source component CVE-2022-33266 A-250627569 * High Closed-source component CVE-2022-33274 A-250627236 * High Closed-source component CVE-2022-33276 A-250627271 * High Closed-source component CVE-2022-33283 A-250627602 * High Closed-source component CVE-2022-33284 A-250627218 * High Closed-source component CVE-2022-33285 A-250627435 * High Closed-source component CVE-2022-33286 A-250627240 * High Closed-source component
Common questions and answersThis 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.
Device manufacturers that include these updates should set the patch string level to:
- Security patch levels of 2023-01-01 or later address all issues associated with the 2023-01-01 security patch level.
- Security patch levels of 2023-01-05 or later address all issues associated with the 2023-01-05 security patch level and all previous patch levels.
For some devices on Android 10 or later, the Google Play system update will have a date string that matches the 2023-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.
Partners are encouraged to bundle the fixes for all issues they are addressing in a single update.
- Devices that use the 2023-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 2023-01-05 or newer must include all applicable patches in this (and previous) security bulletins.
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.
4. What do the entries in the References column mean?
Abbreviation Definition RCE Remote code execution EoP Elevation of privilege ID Information disclosure DoS Denial of service N/A Classification not available
Entries under the References column of the vulnerability details table may contain a prefix identifying the organization to which the reference value belongs.
5. What does an * next to the Android bug ID in the References column mean?
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
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.
Version Date Notes 1.0 January 3, 2022 Bulletin Published
Community Manager•Original Poster
Google Pixel Update - January 2023Announcement
Hello Pixel Community,
We have provided the monthly software update for January 2023. All supported Pixel devices running Android 13 will receive these software updates starting today. The rollout will continue over the next few weeks in phases depending on carrier and device. Users will receive a notification once the OTA becomes available for their device. We encourage you to check your Android version and update to receive the latest software.
Details of this month’s security fixes can be found on the Android Security Bulletin: https://source.android.com/security/bulletin
This update also includes support for static spatial audio, which will provide surround sound for any connected headset. Another update will roll out to Pixel Buds Pro in the coming weeks that will enable spatial audio with head tracking.
Google Pixel Support Team
- Pixel 4a: TQ1A.230105.001
- Pixel 4a (5G): TQ1A.230105.001
- Pixel 5: TQ1A.230105.001
- Pixel 5a (5G): TQ1A.230105.001
- Pixel 6: TQ1A.230105.002
- Pixel 6 Pro: TQ1A.230105.002
- Pixel 6a: TQ1A.230105.001.A2
- Pixel 7: TQ1A.230105.001.A2
- Pixel 7 Pro: TQ1A.230105.002
- Pixel 4a: TQ1A.230105.001.B1
- Pixel 7: TQ1A.230105.001.A3
- Pixel 7 Pro: TQ1A.230105.002.A1
The January 2023 update includes bug fixes and improvements for Pixel users – see below for details.
- Add support for Spatial Audio with certain devices and accessories *
- Additional improvements for fingerprint recognition and response in certain conditions *
- Fix for issue occasionally preventing certain Bluetooth Low Energy devices or accessories from pairing or reconnecting
- Fix for issue preventing audio from playing over certain headphones or accessories while connected in certain conditions
- Fix for issue occasionally causing captured photos to appear corrupted or distorted while zoomed in *
Display & Graphics
- Fix for issue occasionally preventing display from waking or appearing turned off while device is powered on *
- Fix for issue occasionally causing UI to display in landscape layout while device is held in portrait mode
Fixes are available for all supported Pixel devices unless otherwise indicated below.
* Included on Pixel 6, Pixel 6 Pro, Pixel 7, Pixel 7 Pro
* Included on Pixel 6a, Pixel 7
* Included on Pixel 7, Pixel 7 Pro
The answer to life, the universe, and everything.(* I do not claim copyright to this image, nor do I benefit monetarily from it or these posts)
Just kidding (the answer is 42, by the way):
Here there be dragons. I am not responsible for anything at all.
VERY IMPORTANT - On the Pixel 7/Pro, we use Magisk to patch Thanks to @edcsxz, @Lughnasadh, and @AndyYan for news about that and confirming it.
init_boot.img, NOT boot.img AND we flash the patched init_boot to the init_boot partition - do not flash it to the boot partition.
Moved @mariusnoor's provided zero-day OTA.zip to Post #8 - Old news from the OP.
Keep in mind that unlocking the bootloader or rooting might affect your phone's capability to use banking apps such as Google Pay, your local bank's app, or even the ability to install some apps like NetFlix. See Post #2 - Unlocking Bootloader / Rooting / Updating | SafetyNet | ADB/Fastboot & Windows USB Drivers.
There are no permanent negative consequences if you unlock or re-lock the bootloader other than it will wipe your phone, and while your bootloader is unlocked you get a brief screen when you boot the phone telling you (and anyone who sees your phone at the time) that it's unlocked. You will also continue to receive updates (if you've merely unlocked the bootloader, you can take updates as normal) unlike Samsung, Sony, et cetera, which have permanent major consequences with reduced functionality even if you un-root and re-lock your bootloader. If you're actually rooted (not just bootloader unlocked), you'll have to perform extra steps to manually update each month, and to keep root/re-root.
- Post #2 - Unlocking Bootloader / Rooting / Updating | SafetyNet | ADB/Fastboot & Windows USB Drivers:
- How to Root the first time / aka How to unlock the Bootloader
- TL;DR - for the seasoned repeat users
- Unlocking Bootloader (required in order to root)
- How to update each month (and also how to root)[requires an unlocked bootloader for updating via this factory image method]
- OPTIONAL: If you want to flash both slots, after this first time, then after do the following
- Optional steps when updating - flashing custom kernels
- The two schools of thought on disabling Verity and Verification
- ADB/Fastboot and Windows USB Drivers - direct download links and the most recent changelog
- Post #3 - Other, most important resources:
- A list of other important apps
- TWRP [not made for the Pixel 7 (or 6) Pro yet - will update when or if ever it has - don't hold your breath]
- Factory Images (requires an unlocked bootloader)
- Full OTA Images(doesn't require an unlocked bootloader - you can ask questions in this thread, but I won't be providing the steps necessary, as I always use the factory image)
- @mariusnoor's provided official URL to download the zero-day OTA to
- @mariusnoor's provided official URL to download the zero-day OTA to
- Check warranty status
Official Google Pixel Update and Software Repair(reported as of January 23, 2022 to still not be updated for the Pixel 6/Pro - no idea if it has yet now, or if it will be for the 7/Pro)
- Official Google Pixel Install fingerprint calibration software (also available at the bottom of the Update and Software Repair page above) - I believe this is only helpful if you've replaced the screen - if it's anything like the Pixel 6 Pro: if you have the screen replaced, then you *must* have the fingerprint reader replaced as well.
- Find problem apps, Magisk, and LSposed Modules by (three different methods)
- Official Google Android Flash Tool (OEM Unlocking needs to be toggled on - you do not have to manually unlock the bootloader - their site will do that on its own)
- How to determine if you already have Verity and Verification disabled (required for custom kernels for now)
- How to unroot
- Post #4 - Google Pixel Updates (more user-friendly to read than Pixel Update Bulletins) (nothing for the P7P yet)
- Old Google posts/updates
- Post #5 - Pixel Update Bulletins
- Old Bulletins
- Post #6 - Regarding P7P 5G model numbers and capabilities, and how to determine your hardware version
- Post #7 - My personal advice for how to get your device back up and running as you had it before a factory reset
- Post #8 - Old news from the OP
Thank you to the following users who have all contributed greatly to my knowledge of Pixels since I came back to XDA a year ago after a few years of mostly inactivity. Apologies if I miss anybody. In alphabetical order:
- @Az Biker
- @[email protected]
- And many others from all of the previous years who I thanked in my previous OPs.