Local privilege escalation via unchecked psi_write bounds
Published May 14, 2020 · Updated Aug 4, 2024
An out-of-bounds write in the Android kernel scheduler allows local users to escalate privileges without user interaction. The psi_write function in psi.c writes without the required bounds check, causing writes beyond the intended buffer boundary. A local low-privileged process can trigger the condition without additional execution privileges and gain elevated privileges on the device.
Summary
What happened
An out-of-bounds write in the Android kernel scheduler allows local users to escalate privileges without user interaction. The psi_write function in psi.c writes without the required bounds check, causing writes beyond the intended buffer boundary. A local low-privileged process can trigger the condition without additional execution privileges and gain elevated privileges on the device.
The record
- CVE
- CVE-2020-0110
- Published
- May 14, 2020
- Updated
- Aug 4, 2024
- Vendor
- Google Cloud
- Product
- Android
- Classifications
- CWE-787, T1068
- Attack vector
- local
- Privileges
- Unavailable
Timeline
How it unfolded
- May 14, 2020CVE publishedPublication date reported by the CVE source.
- Aug 4, 2024Record 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