自 2025 年 3 月 27 日起，我们建议您使用 android-latest-release 而非 aosp-main 构建 AOSP 并为其做出贡献。如需了解详情，请参阅 AOSP 的变更。
Pixel 更新公告 - 2020 年 7 月
使用集合让一切井井有条
根据您的偏好保存内容并对其进行分类。
发布时间：2020 年 7 月 6 日
本 Pixel 更新公告详细介绍了会影响受支持的 Pixel 设备（以下简称“Google 设备”）的安全漏洞和功能改进。对于 Google 设备，如果安全补丁程序级别是 2020-07-05 或更新，则意味着已解决本公告以及 2020 年 7 月的 Android 安全公告中所述的所有问题。如需了解如何查看设备的安全补丁级别，请参阅查看和更新 Android 版本。
所有受支持的 Google 设备都将会收到 2020-07-05 补丁程序级别的更新。建议所有用户都在自己的设备上接受这些更新。
安全补丁
漏洞按照其影响的组件进行分类，内容包括问题描述和一个表，该表中包含 CVE、相关参考编号、漏洞类型、严重程度和已更新的 Android 开源项目 (AOSP) 版本（若有）。如果有解决相应问题的公开变更记录（例如 AOSP 变更列表），我们会将 bug ID 链接到该记录。如果某个 bug 有多条相关的代码更改记录，我们还会通过 bug ID 后面的数字链接到更多参考内容。
Qualcomm 组件
Qualcomm 闭源组件
| CVE |
参考编号 |
类型 |
严重程度 |
组件 |
| CVE-2019-14101 |
A-147100886* |
N/A |
中 |
闭源组件 |
功能补丁程序
如需详细了解此版本中的新问题修复和功能补丁程序，请参阅 Pixel 社区论坛。
常见问题和解答
这一部分解答了用户在阅读本公告后可能会提出的常见问题。
1. 如何确定我的设备是否已通过更新解决这些问题？
如果安全补丁级别是 2020-07-05 或更新，则意味着已解决 2020-07-05 以及之前的所有安全补丁级别涵盖的所有问题。如需了解如何查看设备的安全补丁级别，请参阅 Google 设备更新时间表中的说明。
2. “类型”列中的条目表示什么意思？
在漏洞详情表内，“类型”列中的条目是安全漏洞的分类。
| 缩写词 |
定义 |
| RCE |
远程代码执行 |
| EoP |
提权 |
| ID |
信息披露 |
| DoS |
拒绝服务攻击 |
| N/A |
没有分类 |
3. “参考编号”列中的条目表示什么意思？
在漏洞详情表内，“参考编号”列中的条目可能包含用于标识参考编号值所属组织的前缀。
| 前缀 |
参考编号 |
| A- |
Android bug ID |
| QC- |
Qualcomm 参考编号 |
| M- |
MediaTek 参考编号 |
| N- |
NVIDIA 参考编号 |
| B- |
Broadcom 参考编号 |
4. 在“参考编号”列中，Android bug ID 旁边的 * 表示什么意思？
如果问题尚未公开发布，在“参考编号”列中，相应 Android bug ID 旁边就会标示 *。Google Developers 网站上针对 Pixel 设备的最新二进制驱动程序中通常包含用于解决相应问题的更新。
5. 为什么要将安全漏洞拆分到本公告和 Android 安全公告中？
如需声明 Android 设备的最新安全补丁级别，必须修复 Android 安全公告中记录的安全漏洞，但修复其他安全漏洞（如本公告中记录的漏洞）则不是必须的。
版本
| 版本 |
日期 |
备注 |
| 1.0 |
2020 年 7 月 6 日 |
发布了本公告 |
本页面上的内容和代码示例受内容许可部分所述许可的限制。Java 和 OpenJDK 是 Oracle 和/或其关联公司的注册商标。
最后更新时间 (UTC)：2025-08-07。
[[["易于理解","easyToUnderstand","thumb-up"],["解决了我的问题","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["没有我需要的信息","missingTheInformationINeed","thumb-down"],["太复杂/步骤太多","tooComplicatedTooManySteps","thumb-down"],["内容需要更新","outOfDate","thumb-down"],["翻译问题","translationIssue","thumb-down"],["示例/代码问题","samplesCodeIssue","thumb-down"],["其他","otherDown","thumb-down"]],["最后更新时间 (UTC)：2025-08-07。"],[],[],null,["# Pixel Update Bulletin—July 2020\n\n*Published July 6, 2020*\n\nThe Pixel Update Bulletin contains details of security vulnerabilities and\nfunctional improvements affecting [supported Pixel devices](https://support.google.com/pixelphone/answer/4457705#pixel_phones&nexus_devices) (Google devices). For Google\ndevices, security patch levels of 2020-07-05 or later\naddress all issues in this bulletin and all issues in the\nJuly 2020 Android Security Bulletin. To learn how to check a\ndevice's security patch level, see [Check and update\nyour Android version](https://support.google.com/pixelphone/answer/4457705).\n\nAll supported Google devices will receive an update to the\n2020-07-05 patch level. We encourage all customers to\naccept these updates to their devices.\n| **Note:** The Google device firmware images are available on the [Google\n| Developer site](https://developers.google.com/android/images).\n\nSecurity patches\n----------------\n\nVulnerabilities are grouped under the component that they affect. There is a\ndescription of the issue and a table with the CVE, associated references, [type of vulnerability](#type), [severity](/docs/security/overview/updates-resources#severity),\nand updated Android Open Source Project (AOSP) versions (where applicable).\nWhen available, we link the public change that addressed the issue to the bug\nID, like the AOSP change list. When multiple changes relate to a single bug,\nadditional references are linked to numbers following the bug ID.\n\n### Qualcomm components\n\n| CVE | References | Type | Severity | Component |\n|----------------|---------------------------------------------------------------------------------------------------------------------------------------------------------|------|----------|------------------|\n| CVE-2019-14037 | A-130873956 [QC-CR#2251042 \\[2\\]](https://www.codeaurora.org/gitweb/quic/la/?p=kernel/msm-3.18.git;a=commit;h=e73a43245a3055182c1352f9886bd0fc5f12af84) | N/A | Moderate | Kernel |\n| CVE-2019-14093 | A-139417368 [QC-CR#2517976](https://source.codeaurora.org/quic/la/platform/hardware/qcom/display/commit/?id=acd2e5735fde366c2c4c98ac70fc4995c7af61dc) | N/A | Moderate | Display/graphics |\n| CVE-2019-14100 | A-147100689 [QC-CR#2528072](https://source.codeaurora.org/quic/la/kernel/msm-4.14/commit/?id=de8810cf37cf494441c2987be03f7a086ed54f76) | N/A | Moderate | Kernel |\n\n### Qualcomm closed-source\ncomponents\n\n| CVE | References | Type | Severity | Component |\n|----------------|----------------------------|------|----------|-------------------------|\n| CVE-2019-14101 | A-147100886[\\*](#asterisk) | N/A | Moderate | Closed-source component |\n\nFunctional patches\n------------------\n\nFor details on the new bug fixes and functional patches included in this\nrelease, refer to the [Pixel Community\nforum](https://support.google.com/pixelphone/thread/57451355).\n\nCommon questions and answers\n----------------------------\n\n\nThis section answers common questions that may occur after reading this\nbulletin.\n\n\n**1. How do I determine if my device is updated to address these issues?**\n\nSecurity patch levels of 2020-07-05 or later address all issues associated with the 2020-07-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](https://support.google.com/pixelphone/answer/4457705#pixel_phones&nexus_devices).\n\n\n**2. What do the entries in the *Type* column mean?**\n\nEntries in the *Type* column of the vulnerability details table\nreference the classification of the security vulnerability.\n\n| Abbreviation | Definition |\n|--------------|------------------------------|\n| RCE | Remote code execution |\n| EoP | Elevation of privilege |\n| ID | Information disclosure |\n| DoS | Denial of service |\n| N/A | Classification not available |\n\n\n**3. What do the entries in the *References* column mean?**\n\nEntries under the *References* column of the vulnerability details\ntable may contain a prefix identifying the organization to which the reference\nvalue belongs.\n\n| Prefix | Reference |\n|--------|---------------------------|\n| A- | Android bug ID |\n| QC- | Qualcomm reference number |\n| M- | MediaTek reference number |\n| N- | NVIDIA reference number |\n| B- | Broadcom reference number |\n\n\n**4. What does an \\* next to the Android bug ID in the *References*\ncolumn mean?**\n\nIssues that are not publicly available have an \\* next to the Android bug ID\nin the *References* column. The update for that issue is generally\ncontained in the latest binary drivers for Pixel devices available from the\n[Google Developer site](https://developers.google.com/android/drivers).\n\n\n**5. Why are security vulnerabilities split between this bulletin and the\nAndroid Security Bulletins?**\n\nSecurity vulnerabilities that are documented in the Android Security\nBulletins are required to declare the latest security patch level on Android\ndevices. Additional security vulnerabilities, such as those documented in this\nbulletin are not required for declaring a security patch level.\n\nVersions\n--------\n\n| Version | Date | Notes |\n|---------|--------------|--------------------|\n| 1.0 | July 6, 2020 | Bulletin published |"]]
