Kernel privilege escalation via packet hook race
Published Dec 4, 2024 · Updated Dec 5, 2024
Use-after-free in the Android kernel network stack allows local users with System execution privileges to gain kernel privileges. Improper locking between __unregister_prot_hook and packet_release in af_packet.c permits packet state to be freed while it remains in use. The flaw needs no user interaction, but existing System-level local code execution is required to reach the further kernel compromise.
Summary
What happened
Use-after-free in the Android kernel network stack allows local users with System execution privileges to gain kernel privileges. Improper locking between __unregister_prot_hook and packet_release in af_packet.c permits packet state to be freed while it remains in use. The flaw needs no user interaction, but existing System-level local code execution is required to reach the further kernel compromise.
The record
- CVE
- CVE-2018-9439
- Published
- Dec 4, 2024
- Updated
- Dec 5, 2024
- Vendor
- Product
- Google Pixel
- Classifications
- CWE-416, T1068
- Attack vector
- local
- Privileges
- admin
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-08-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.
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