Local privilege escalation via LWIS heap overflow
Published Jan 3, 2025 · Updated Jan 3, 2025
Heap buffer overflow in the Android LWIS kernel driver allows local users to escalate privileges through a crafted IOCTL transaction. construct_transaction_from_cmd in lwis_ioctl.c writes beyond a heap allocation while constructing a transaction from an untrusted command. Low-privileged local access to an affected Pixel device is required; exploitation needs no user interaction and grants elevated privileges.
Summary
What happened
Heap buffer overflow in the Android LWIS kernel driver allows local users to escalate privileges through a crafted IOCTL transaction. construct_transaction_from_cmd in lwis_ioctl.c writes beyond a heap allocation while constructing a transaction from an untrusted command. Low-privileged local access to an affected Pixel device is required; exploitation needs no user interaction and grants elevated privileges.
The record
- CVE
- CVE-2024-47032
- Published
- Jan 3, 2025
- Updated
- Jan 3, 2025
- Vendor
- Google Cloud
- Product
- Android
- Classifications
- CWE-120, T1404
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jan 3, 2025CVE publishedPublication date reported by the CVE source.
- Jan 3, 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.
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