Kernel privilege escalation via unchecked buffer writes
Published Dec 4, 2024 · Updated Dec 5, 2024
Kernel buffer overwrite in Google Android before the 2018-06-05 patch level allows attackers to elevate privileges through the WLAN driver. Multiple functions in gl_proc.c copy input into a buffer without checking its bounds, overwriting adjacent kernel memory. The vendor identifies a MediaTek WLAN driver path but does not publish the exact input route; successful corruption elevates privileges in the kernel.
Summary
What happened
Kernel buffer overwrite in Google Android before the 2018-06-05 patch level allows attackers to elevate privileges through the WLAN driver. Multiple functions in gl_proc.c copy input into a buffer without checking its bounds, overwriting adjacent kernel memory. The vendor identifies a MediaTek WLAN driver path but does not publish the exact input route; successful corruption elevates privileges in the kernel.
The record
- CVE
- CVE-2018-9402
- Published
- Dec 4, 2024
- Updated
- Dec 5, 2024
- Vendor
- Product
- Google Pixel
- Classifications
- CWE-120, CWE-787, T1068
- Attack vector
- Unavailable
- Privileges
- authenticated
Timeline
How it unfolded
- Dec 4, 2024CVE publishedPublication date reported by the CVE source.
- Dec 5, 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=0 <2018-06-05
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.
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