Local service interruption via unchecked GPU read
Published Dec 4, 2023 · Updated Aug 2, 2024
Out-of-bounds read in UNISOC Android 11 GPU drivers allows local users with System privileges to interrupt service. The driver reads beyond the intended GPU buffer because it performs the read without the required bounds check. System-level execution privileges are required, and the documented consequence is a local service interruption rather than remote compromise.
Summary
What happened
Out-of-bounds read in UNISOC Android 11 GPU drivers allows local users with System privileges to interrupt service. The driver reads beyond the intended GPU buffer because it performs the read without the required bounds check. System-level execution privileges are required, and the documented consequence is a local service interruption rather than remote compromise.
The record
- CVE
- CVE-2023-42725
- Published
- Dec 4, 2023
- Updated
- Aug 2, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-125, CAPEC-540, T1499.004
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Dec 4, 2023CVE publishedPublication date reported by the CVE source.
- Aug 2, 2024Record 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