Local service interruption via unchecked driver write
Published Jun 6, 2023 · Updated Jan 7, 2025
An out-of-bounds write in the cp_dump driver on Unisoc chipsets running Android 11 through Android 13 allows local users to interrupt service. The cp_dump kernel driver omits a bounds check before a write, allowing data to pass beyond the intended buffer. System-level execution privileges and user interaction are required, and the documented consequence is a local service interruption.
Summary
What happened
An out-of-bounds write in the cp_dump driver on Unisoc chipsets running Android 11 through Android 13 allows local users to interrupt service. The cp_dump kernel driver omits a bounds check before a write, allowing data to pass beyond the intended buffer. System-level execution privileges and user interaction are required, and the documented consequence is a local service interruption.
The record
- CVE
- CVE-2022-48438
- Published
- Jun 6, 2023
- Updated
- Jan 7, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-787, T1499
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Jun 6, 2023CVE publishedPublication date reported by the CVE source.
- Jan 7, 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