Local privilege escalation via LWIS out-of-bounds write
Published Jan 3, 2025 · Updated Jan 6, 2025
Out-of-bounds write in the LWIS kernel driver on supported Google Pixel devices allows local users to escalate privileges. The prepare_response_locked function in lwis_transaction.c insufficiently validates transaction response data before writing it beyond an intended buffer boundary. Exploitation requires local low-privileged access but no user interaction or additional execution privileges, and successful corruption grants elevated execution on the device.
Summary
What happened
Out-of-bounds write in the LWIS kernel driver on supported Google Pixel devices allows local users to escalate privileges. The prepare_response_locked function in lwis_transaction.c insufficiently validates transaction response data before writing it beyond an intended buffer boundary. Exploitation requires local low-privileged access but no user interaction or additional execution privileges, and successful corruption grants elevated execution on the device.
The record
- CVE
- CVE-2024-53833
- Published
- Jan 3, 2025
- Updated
- Jan 6, 2025
- Vendor
- Google Cloud
- Product
- Android
- Classifications
- CWE-787, T1404
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jan 3, 2025CVE publishedPublication date reported by the CVE source.
- Jan 6, 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?
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.
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