Kernel denial of service via unchecked sensor write
Published Oct 14, 2022 · Updated May 14, 2025
An out-of-bounds write in the UNISOC sensor driver on affected Android 10–12 chipsets allows local users to crash the kernel. The driver omits a bounds check when handling sensor data, permitting a write beyond the intended memory buffer; UNISOC does not identify the specific function or input path. Local high-privileged access and user interaction are required, and the documented consequence is limited to kernel denial of service.
Summary
What happened
An out-of-bounds write in the UNISOC sensor driver on affected Android 10–12 chipsets allows local users to crash the kernel. The driver omits a bounds check when handling sensor data, permitting a write beyond the intended memory buffer; UNISOC does not identify the specific function or input path. Local high-privileged access and user interaction are required, and the documented consequence is limited to kernel denial of service.
The record
- CVE
- CVE-2022-39125
- Published
- Oct 14, 2022
- Updated
- May 14, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-400, T1499.004
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Oct 14, 2022CVE publishedPublication date reported by the CVE source.
- May 14, 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.
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