自 2025 年 3 月 27 日起，我们建议您使用 android-latest-release 而非 aosp-main 构建 AOSP 并为其做出贡献。如需了解详情，请参阅 AOSP 的变更。
Android 安全公告 - 2025 年 7 月
使用集合让一切井井有条
根据您的偏好保存内容并对其进行分类。
发布时间：2025 年 7 月 7 日
Android 安全公告详细介绍了会影响 Android 设备的安全漏洞。如果安全补丁级别是 2025-07-05 或更高级别，就意味着已解决本公告中所述的所有问题。
如需了解如何查看设备的安全补丁级别，请参阅查看和更新 Android 版本。
Android 合作伙伴在本公告发布前至少一个月就已收到所有问题的相关通知。我们会在接下来的 48 小时内将针对这些问题的源代码补丁程序发布到 Android 开源项目 (AOSP) 代码库中。届时，我们将会修订本公告，将相关 AOSP 链接增补到本文中。
通告
- 2025 年 7 月的 Android 安全公告中没有 Android 安全补丁。
请参阅 Android 和 Google Play 保护机制提供的缓解措施部分，详细了解有助于提高 Android 平台安全性的 Android 安全平台防护功能和 Google Play 保护机制。
Android 和 Google 服务缓解措施
这一部分总结了 Android 安全平台和服务防护功能（如 Google Play 保护机制）提供的缓解措施。这些功能有助于降低 Android 上的安全漏洞被成功利用的可能性。
- 较高版本的 Android 平台中提供的增强功能让攻击者更加难以利用 Android 上存在的许多问题。我们建议所有用户都尽可能更新到最新版 Android。
- Android 安全团队会积极利用 Google Play 保护机制监控滥用行为，并会在发现潜在有害应用时向用户发出警告。在安装有 Google 移动服务的设备上，Google Play 保护机制默认处于启用状态，对于从 Google Play 以外的来源安装应用的用户来说，该功能尤为重要。
常见问题和解答
这一部分解答了用户在阅读本公告后可能会提出的常见问题。
1. 如何确定我的设备是否已通过更新解决了这些问题？
如需了解如何查看设备的安全补丁级别，请参阅查看和更新 Android 版本。
- 如果安全补丁级别是 2025-07-01 或更高级别，就意味着已解决 2025-07-01 安全补丁级别涵盖的所有问题。
- 如果安全补丁级别是 2025-07-05 或更高级别，就意味着已解决 2025-07-05 以及之前的所有安全补丁级别涵盖的所有问题。
预装这些更新的设备制造商应将补丁字符串级别设为：
- [ro.build.version.security_patch]:[2025-07-01]
- [ro.build.version.security_patch]:[2025-07-05]
对于某些搭载 Android 10 或更高版本的设备，Google Play 系统更新的日期字符串将与 2025-07-01 安全补丁级别一致。
如需详细了解如何安装安全更新，请查看这篇文章。
2. 为何本公告有 2 个安全补丁级别？
本公告之所以有 2 个安全补丁级别，是为了让 Android 合作伙伴能够灵活地、更快速地修复在各种 Android 设备上都有发现的一部分相似漏洞。我们建议 Android 合作伙伴修复本公告中的所有问题并使用最新的安全补丁级别。
- 如果设备使用的是 2025-07-01 这一安全补丁级别，则必须包含该安全补丁级别涵盖的所有问题以及之前的安全公告中报告的所有问题的修复程序。
- 如果设备使用的是 2025-07-05 或更新的安全补丁级别，就必须包含本安全公告（以及之前的安全公告）中的所有适用补丁。
我们建议合作伙伴将要解决的全部问题的修复程序打包到一个更新中。
3. “类型”列中的条目表示什么意思？
在漏洞详情表内，“类型”列中的条目是安全漏洞的分类。
| 缩写词 |
定义 |
| RCE |
远程代码执行 |
| EoP |
提权 |
| ID |
信息披露 |
| DoS |
拒绝服务攻击 |
| 不适用 |
没有分类 |
4. “参考编号”列中的条目表示什么意思？
在漏洞详情表内，“参考编号”列中的条目可能包含用于标识参考编号值所属组织的前缀。
| 前缀 |
参考编号 |
| A- |
Android bug ID |
| QC- |
Qualcomm 参考编号 |
| M- |
MediaTek 参考编号 |
| N- |
NVIDIA 参考编号 |
| B- |
Broadcom 参考编号 |
| U- |
UNISOC 参考编号 |
5. 在“参考编号”列中，Android bug ID 旁边的 * 表示什么意思？
如果问题尚未公开发布，在“参考编号”列中，相应 Android bug ID 旁边就会显示 *。Google Developers 网站上针对 Pixel 设备提供的最新二进制驱动程序中通常包含旨在解决相应问题的更新。
6. 为什么将安全漏洞拆分到本公告和设备 /合作伙伴安全公告（如 Pixel 公告）中？
如需声明 Android 设备的最新安全补丁级别，必须修复本安全公告中记录的安全漏洞，但在声明安全补丁级别时，并不是必须修复设备/ 合作伙伴安全公告中记录的其他安全漏洞。Android 设备和芯片组制造商可能也会发布针对其产品的安全漏洞详情，例如：Google、Huawei、LGE、Motorola、Nokia或Samsung。
版本
| 版本 |
日期 |
备注 |
| 1.0 |
2025 年 7 月 7 日 |
发布了本公告 |
本页面上的内容和代码示例受内容许可部分所述许可的限制。Java 和 OpenJDK 是 Oracle 和/或其关联公司的注册商标。
最后更新时间 (UTC)：2025-08-12。
[[["易于理解","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-12。"],[],[],null,["# Android Security Bulletin—July 2025\n\n*Published July 7, 2025*\n\nThe Android Security Bulletin contains details of security vulnerabilities\naffecting Android devices. Security patch levels of\n2025-07-05 or later address all of these issues.\nTo learn how to check a device's security patch level, see\n[Check and update your Android version](https://support.google.com/pixelphone/answer/4457705).\n\nAndroid partners are notified of all issues at least a month before\npublication.\nSource code patches for these issues will be released to the Android Open\nSource Project (AOSP) repository in the next 48 hours. We will revise this\nbulletin with the AOSP links when they are available.\n\nAnnouncements\n-------------\n\n- There are no Android security patches in the July 2025 Android Security Bulletin.\n\nRefer to the [Android and Google Play Protect\nmitigations](#mitigations) section for details on the\n[Android security platform protections](/security/enhancements)\nand Google Play Protect, which improve the security of the Android platform.\n\nAndroid and Google service mitigations\n--------------------------------------\n\nThis is a summary of the mitigations provided by the\n[Android security platform](/security/enhancements) and service\nprotections such as\n[Google Play\nProtect](https://developers.google.com/android/play-protect). These capabilities reduce the likelihood that security\nvulnerabilities could be successfully exploited on Android.\n\n- 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.\n- The Android security team actively monitors for abuse through [Google Play\n Protect](https://developers.google.com/android/play-protect) and warns users about [Potentially\n Harmful Applications](/static/security/reports/Google_Android_Security_PHA_classifications.pdf). Google Play Protect is enabled by default on devices with [Google Mobile\n Services](http://www.android.com/gms), and is especially important for users who install apps from outside of Google Play.\n\nCommon questions and answers\n----------------------------\n\nThis section answers common questions that may occur after reading this\nbulletin.\n\n**1. How do I determine if my device is updated to address these\nissues?**\n\nTo learn how to check a device's security patch level, see\n[Check and update your Android version](https://support.google.com/pixelphone/answer/4457705#pixel_phones&nexus_devices).\n\n- Security patch levels of 2025-07-01 or later address all issues associated with the 2025-07-01 security patch level.\n- Security patch levels of 2025-07-05 or later address all issues associated with the 2025-07-05 security patch level and all previous patch levels.\n\nDevice manufacturers that include these updates should set the patch string level to:\n\n- \\[ro.build.version.security_patch\\]:\\[2025-07-01\\]\n- \\[ro.build.version.security_patch\\]:\\[2025-07-05\\]\n\nFor some devices on Android 10 or later, the Google Play system update\nwill have a date string that matches the 2025-07-01\nsecurity patch level.\nPlease see [this\narticle](https://support.google.com/android/answer/7680439) for more details on how to install\nsecurity updates.\n\n**2. Why does this bulletin have two security patch levels?**\n\nThis bulletin has two security patch levels so that Android partners have the\nflexibility to fix a subset of vulnerabilities that are similar across all\nAndroid devices more quickly. Android partners are encouraged to fix all issues\nin this bulletin and use the latest security patch level.\n\n- Devices that use the 2025-07-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.\n- Devices that use the security patch level of 2025-07-05 or newer must include all applicable patches in this (and previous) security bulletins.\n\nPartners are encouraged to bundle the fixes for all issues they are\naddressing in a single update.\n\n\n**3. 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**4. 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| U- | UNISOC reference number |\n\n\n**5. 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 corresponding\nreference ID. The update for that issue is generally contained in the latest\nbinary drivers for Pixel devices available from the\n[Google Developer site](https://developers.google.com/android/drivers).\n\n**6. Why are security vulnerabilities split between this bulletin and\ndevice/partner security bulletins, such as the\nPixel bulletin?**\n\nSecurity vulnerabilities that are documented in this security bulletin are\nrequired to declare the latest security patch level on Android\ndevices. Additional security vulnerabilities that are documented in the\ndevice/partner security bulletins are not required for\ndeclaring a security patch level. Android device and chipset manufacturers\nmay also publish security vulnerability details specific to their products,\nsuch as\n[Google](/docs/security/bulletin/pixel),\n[Huawei](https://consumer.huawei.com/en/support/bulletin/),\n[LGE](https://lgsecurity.lge.com/security_updates_mobile.html),\n[Motorola](https://motorola-global-portal.custhelp.com/app/software-security-page/g_id/6806),\n[Nokia](https://www.nokia.com/phones/en_int/security-updates), or\n[Samsung](https://security.samsungmobile.com/securityUpdate.smsb).\n\nVersions\n--------\n\n| Version | Date | Notes |\n|---------|--------------|--------------------|\n| 1.0 | July 7, 2025 | Bulletin Published |"]]
