Kernel crash via missing sensor-driver bounds check
Published Oct 14, 2022 · Updated May 15, 2025
Buffer overflow in the UNISOC sensor driver for Android 10, 11, and 12 allows local users to crash the kernel through an out-of-bounds write. The driver performs a write without the required bounds check; UNISOC has not disclosed the affected function, buffer, or input field. Exploitation requires local access, high privileges, and user interaction, and the documented consequence is a kernel crash rather than code execution.
Summary
What happened
Buffer overflow in the UNISOC sensor driver for Android 10, 11, and 12 allows local users to crash the kernel through an out-of-bounds write. The driver performs a write without the required bounds check; UNISOC has not disclosed the affected function, buffer, or input field. Exploitation requires local access, high privileges, and user interaction, and the documented consequence is a kernel crash rather than code execution.
The record
- CVE
- CVE-2022-39120
- Published
- Oct 14, 2022
- Updated
- May 15, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-120, T1642
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Oct 14, 2022CVE publishedPublication date reported by the CVE source.
- May 15, 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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