Local privilege escalation via inconsistent self-registration flags
Published Aug 26, 2025 · Updated Aug 27, 2025
Privilege escalation in Android 12 through 15 allows local users to bypass SELinux through ServiceManager self-registration. In cmds/servicemanager/main.cpp, ServiceManager self-registers without enabling requesting-SID handling, leaving its identity flags inconsistent. Local users need no additional execution privileges or user interaction to cross the policy boundary and gain elevated privileges.
Summary
What happened
Privilege escalation in Android 12 through 15 allows local users to bypass SELinux through ServiceManager self-registration. In cmds/servicemanager/main.cpp, ServiceManager self-registers without enabling requesting-SID handling, leaving its identity flags inconsistent. Local users need no additional execution privileges or user interaction to cross the policy boundary and gain elevated privileges.
The record
- CVE
- CVE-2025-0078
- Published
- Aug 26, 2025
- Updated
- Aug 27, 2025
- Vendor
- Google Cloud
- Product
- Android
- Classifications
- CWE-250, T1404
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 26, 2025CVE publishedPublication date reported by the CVE source.
- Aug 27, 2025Record 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=12
- Affected versionversion=12L
- Affected versionversion=13
- Affected versionversion=14
- Affected versionversion=15
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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.
Weakness, pattern, technique
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