Local service interruption via PackageInstaller memory exhaustion
Published Jun 17, 2026 · Updated Jun 17, 2026
Memory exhaustion in Android 17 PackageInstaller.Session#transfer allows local users to interrupt device service without user interaction. The transfer implementation in PackageInstallerSession.java contains a logic error, but Google has not disclosed the erroneous operation or attacker-controlled input. No additional execution privileges are needed; successful exhaustion can make the device unavailable, with no reported confidentiality or integrity impact.
Summary
What happened
Memory exhaustion in Android 17 PackageInstaller.Session#transfer allows local users to interrupt device service without user interaction. The transfer implementation in PackageInstallerSession.java contains a logic error, but Google has not disclosed the erroneous operation or attacker-controlled input. No additional execution privileges are needed; successful exhaustion can make the device unavailable, with no reported confidentiality or integrity impact.
The record
- CVE
- CVE-2026-28575
- Published
- Jun 17, 2026
- Updated
- Jun 17, 2026
- Vendor
- Go standard library
- Product
- Android
- Classifications
- CWE-400, T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 17, 2026CVE publishedPublication date reported by the CVE source.
- Jun 17, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=17
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo