Kernel denial of service via unchecked JPG bounds
Published Oct 14, 2022 · Updated May 15, 2025
Out-of-bounds write in the UNISOC JPG driver on Android 10 through 12 allows local users to cause a kernel denial of service. The driver performs an out-of-bounds heap write because a required bounds check is missing; UNISOC has not disclosed the affected function or input field. Exploitation requires local access to a device using an affected UNISOC chipset, and the documented consequence is interruption of the kernel.
Summary
What happened
Out-of-bounds write in the UNISOC JPG driver on Android 10 through 12 allows local users to cause a kernel denial of service. The driver performs an out-of-bounds heap write because a required bounds check is missing; UNISOC has not disclosed the affected function or input field. Exploitation requires local access to a device using an affected UNISOC chipset, and the documented consequence is interruption of the kernel.
The record
- CVE
- CVE-2022-2984
- Published
- Oct 14, 2022
- Updated
- May 15, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-787, T1499
- 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