Kernel interruption via missing face-driver bounds check
Published Dec 6, 2022 · Updated Apr 24, 2025
An out-of-bounds write in UNISOC's face-detection driver allows local users to interrupt kernel availability via crafted input. UNISOC labels the issue a buffer over-read and CWE-126, while its description states that a missing bounds check permits an out-of-bounds write. Local access to an affected device is required, and UNISOC has not specified whether triggering causes a hang, crash, or reboot.
Summary
What happened
An out-of-bounds write in UNISOC's face-detection driver allows local users to interrupt kernel availability via crafted input. UNISOC labels the issue a buffer over-read and CWE-126, while its description states that a missing bounds check permits an out-of-bounds write. Local access to an affected device is required, and UNISOC has not specified whether triggering causes a hang, crash, or reboot.
The record
- CVE
- CVE-2022-39130
- Published
- Dec 6, 2022
- Updated
- Apr 24, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-126, T1642
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 6, 2022CVE publishedPublication date reported by the CVE source.
- Apr 24, 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.
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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