Kernel denial of service via unchecked buffer write
Published Feb 6, 2023 · Updated Mar 26, 2025
An out-of-bounds write in the UNISOC GPU driver on Android 10 through Android 12 allows local users to interrupt the kernel. The driver performs a buffer write without the required bounds check, but UNISOC has not disclosed the affected function or input path. Exploitation requires high local privileges and user interaction; the resulting kernel denial of service is documented, but its interruption mode is undisclosed.
Summary
What happened
An out-of-bounds write in the UNISOC GPU driver on Android 10 through Android 12 allows local users to interrupt the kernel. The driver performs a buffer write without the required bounds check, but UNISOC has not disclosed the affected function or input path. Exploitation requires high local privileges and user interaction; the resulting kernel denial of service is documented, but its interruption mode is undisclosed.
The record
- CVE
- CVE-2022-38675
- Published
- Feb 6, 2023
- Updated
- Mar 26, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-787, CWE-121, T1642
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Feb 6, 2023CVE publishedPublication date reported by the CVE source.
- Mar 26, 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