Local service interruption via missing bounds check
Published Jan 18, 2024 · Updated Jun 20, 2025
Out-of-bounds write in phasecheckserver on Unisoc chipsets running Android 11 through 13 allows local users to interrupt service. A missing bounds check permits phasecheckserver to write beyond the intended buffer while processing input. Low-privileged local access is required; Unisoc does not disclose the input path or whether the resulting interruption is a hang or crash.
Summary
What happened
Out-of-bounds write in phasecheckserver on Unisoc chipsets running Android 11 through 13 allows local users to interrupt service. A missing bounds check permits phasecheckserver to write beyond the intended buffer while processing input. Low-privileged local access is required; Unisoc does not disclose the input path or whether the resulting interruption is a hang or crash.
The record
- CVE
- CVE-2023-48352
- Published
- Jan 18, 2024
- Updated
- Jun 20, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-787, T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jan 18, 2024CVE publishedPublication date reported by the CVE source.
- Jun 20, 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