Kernel denial of service via unchecked sensor write
Published Oct 14, 2022 · Updated May 15, 2025
Integer overflow in the UNISOC sensor driver on affected Android 10 through Android 12 chipsets allows local users to interrupt the kernel. The driver fails to check a write boundary, allowing an integer overflow to produce an out-of-bounds write in kernel memory; no function or patch diff is public. Local access to an affected chipset is required, and the documented consequence is kernel availability loss rather than data disclosure.
Summary
What happened
Integer overflow in the UNISOC sensor driver on affected Android 10 through Android 12 chipsets allows local users to interrupt the kernel. The driver fails to check a write boundary, allowing an integer overflow to produce an out-of-bounds write in kernel memory; no function or patch diff is public. Local access to an affected chipset is required, and the documented consequence is kernel availability loss rather than data disclosure.
The record
- CVE
- CVE-2022-39105
- Published
- Oct 14, 2022
- Updated
- May 15, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-190, T1642
- Attack vector
- local
- Privileges
- Unavailable
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