Local privilege escalation via parameter buffer overwrite
Published Mar 24, 2023 · Updated Feb 25, 2025
An out-of-bounds write in the GSC component of Google Pixel Android kernel allows local users to escalate privileges. The append_to_params function in param_util.c applies an incorrect bounds check while appending parameter data, permitting a write past the destination buffer. Exploitation requires local low-privileged execution but no user interaction, and successful memory corruption grants higher privileges.
Summary
What happened
An out-of-bounds write in the GSC component of Google Pixel Android kernel allows local users to escalate privileges. The append_to_params function in param_util.c applies an incorrect bounds check while appending parameter data, permitting a write past the destination buffer. Exploitation requires local low-privileged execution but no user interaction, and successful memory corruption grants higher privileges.
The record
- CVE
- CVE-2023-21041
- Published
- Mar 24, 2023
- Updated
- Feb 25, 2025
- Vendor
- Product
- Google Pixel
- Classifications
- CWE-787, T1068
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 24, 2023CVE publishedPublication date reported by the CVE source.
- Feb 25, 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