Published November 4, 2019 | Updated December 5, 2019
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 2019-11-05 or later address all issues in this bulletin and all issues in the November 2019 Android Security Bulletin. To learn how to check a device's security patch level, see Check & update your Android version.
All supported Google devices will receive an update to the 2019-11-05 patch level. We encourage all customers to accept these updates for their devices.
- In addition to the security vulnerabilities described in the November 2019 Android Security Bulletin, Google devices also contain patches for the security vulnerabilities described below.
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.
|CVE||References||Type||Severity||Updated AOSP versions|
Qualcomm closed-source components
These updates are included for affected Google devices to address functionality issues not related to the security of Google devices. The table includes associated references; the affected category, such as Bluetooth or mobile data; improvements; and affected devices.
|A-135756211||Assistant||Improvements for Google Assistant Hotword||Pixel 2, Pixel 2 XL, Pixel 3, Pixel 3 XL|
|A-139313340||Audio||Improvements for bottom speaker audio quality||Pixel 3|
|A-139402097||Stability||Additional fixes for some devices stuck during boot||Pixel 3, Pixel 3 XL, Pixel 3a, Pixel 3a XL|
|A-140808513||Keyboards||Additional support for Xbox BT controller mapping||Pixel 2, Pixel 2 XL, Pixel 3, Pixel 3 XL, Pixel 3a, Pixel 3a XL, Pixel 4, Pixel 4 XL|
|Various||Display/Graphics||Smooth Display improvements||Pixel 4, Pixel 4 XL|
|Various||Camera||Camera quality improvements||Pixel 4, Pixel 4 XL|
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 2019-11-05 or later address all issues associated with the 2019-11-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.
|RCE||Remote code execution|
|EoP||Elevation of privilege|
|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.
|A-||Android bug ID|
|QC-||Qualcomm reference number|
|M-||MediaTek reference number|
|N-||NVIDIA reference number|
|B-||Broadcom 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.
|1.0||November 4, 2019||Bulletin published.|
|1.1||December 5, 2019||Corrected CVE number for CVE-2019-9503.|