Android security tags, read closely by Lightrion

June 2025: the bulletin, and what actually shipped

The bulletin lists CVEs. The public security tags carry the code. This page joins the two for Android 14 to 17: which CVEs have a public fix in each major's tags, which do not, and what the tags fix that no bulletin mentions.

At a glance

MajorCVEs for it FixedProbableNo public code Security tags this month
Android 14141400android-security-14.0.0_r21
Android 15161600android-security-15.0.0_r9
Android 16 (pre-release, 16-next)161500none
Android 17 (pre-release, 17-next)0000none

The bulletin also has 18 vendor and kernel rows (closed-source components, kernel LTS) with no AOSP code to check; they are not counted above.

What this month's security tags add

Each security tag published this month, and the CVEs whose public fix first appears in it. CVEs resolved by an earlier tag are not repeated here; they are in the table above and on each CVE page.

android-security-14.0.0_r21 adds the fix for 13 CVEs: CVE-2025-26443, CVE-2025-26445, CVE-2025-26448, CVE-2025-26449, CVE-2025-26450, CVE-2025-26452, CVE-2025-26453, CVE-2025-26455, CVE-2025-26456, CVE-2025-26458, CVE-2025-26462, CVE-2025-26463, CVE-2025-32312.

android-security-15.0.0_r9 adds the fix for 15 CVEs: CVE-2025-26432, CVE-2025-26437, CVE-2025-26443, CVE-2025-26445, CVE-2025-26448, CVE-2025-26449, CVE-2025-26450, CVE-2025-26452, CVE-2025-26453, CVE-2025-26455, CVE-2025-26456, CVE-2025-26458, CVE-2025-26462, CVE-2025-26463, CVE-2025-32312.

Announced, with no public code

None this month.

Announced, but the patched code is not there

No fix in the tags, and none of the code the bulletin's commit patches exists in these majors: it was removed or reworked before their release (probable).

CVE-2025-26432, High DoS
Android 16. none of 2 lines the fix of reference a928f3273592 modifies or sits in exists in android-security-16.0.0_r9 (e.g. 'mAssociationRequestsProcessor.setAssociationTag(associationId, tag);'): the patched code is not in this major

Public before it was announced

The fixing commit was in a public security tag before the bulletin announced the CVE.

CVEMajors (tag where the fix is complete)Public sinceDays early
CVE-2025-2644114 (r20), 15 (r8)2025-05-0527

Fixed, by a probable match

None this month.

Security fixes no advisory mentions

Commits of this month's security tags whose bug ids are in no bulletin and no OSV advisory. Some are likely lower-severity fixes, some may become CVEs later.

Android 14: 1 fix in android-security-14.0.0_r21

Show the list
Display the system gallery storage permission as system fixed
Bug 315320090; android-security-14.0.0_r21
packages/modules/Permission 89b9ab0ec7a4

Android 15: 2 fixes in android-security-15.0.0_r9

Show the list
Disable ASM_RESTRICTIONS flag
Bug 367702727; android-security-15.0.0_r9
frameworks/base 48a022f29de5
Display the system gallery storage permission as system fixed
Bug 315320090; android-security-15.0.0_r9
packages/modules/Permission 1c4928bbc6d3

Fix analysis AI-generated

For each CVE with a public fix, an analysis of Google's patch: root cause, how the fix works, what it covers and leaves out. Written by a model from the bulletin and the fixing diffs, then checked against the code by a second model. It can still be wrong: verify against the commit.

Bulletin revisions

VersionDateNotes
1.0June 2, 2025Bulletin Published
1.1June 2, 2025AOSP links added

Method and limits

Fixes are found in the public android-security-* tags by the bug id in the commit message, then Change-Id and patch id against the bulletin's commit, then two probable matches checked by content. "No public code" means no fixing commit in the ingested tags of that major, not proof that no fix exists anywhere. When none of the code the bulletin's commit patches exists in a major (removed or reworked before its release), the CVE is shown as "patched code absent" instead. Vendor closed-source components and the kernel are out of scope.

Data for this page (JSON).