Local privilege escalation via signal criteria overwrite
Published Dec 16, 2022 · Updated Apr 17, 2025
An out-of-bounds write in the Android kernel allows local users with System privileges to gain elevated privileges without interaction. ProtocolMiscBuilder::BuildSetSignalReportCriteria in protocolmiscbuilder.cpp applies an incorrect bounds check before writing signal-report criteria beyond allocated memory. Exploitation requires local System-level execution and can corrupt adjacent memory to obtain higher privileges; no user interaction is required.
Summary
What happened
An out-of-bounds write in the Android kernel allows local users with System privileges to gain elevated privileges without interaction. ProtocolMiscBuilder::BuildSetSignalReportCriteria in protocolmiscbuilder.cpp applies an incorrect bounds check before writing signal-report criteria beyond allocated memory. Exploitation requires local System-level execution and can corrupt adjacent memory to obtain higher privileges; no user interaction is required.
The record
- CVE
- CVE-2022-42505
- Published
- Dec 16, 2022
- Updated
- Apr 17, 2025
- Vendor
- Google Cloud
- Product
- Android
- Classifications
- CWE-787, T1404
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Dec 16, 2022CVE publishedPublication date reported by the CVE source.
- Apr 17, 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=Android kernel
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