Service interruption via unchecked modem-control write
Published May 9, 2023 · Updated Jan 28, 2025
Out-of-bounds write in modem control code on UNISOC Android 10 chipsets allows local users to interrupt service via unspecified vectors. The modem control device performs a write without the required bounds check, allowing memory outside the intended buffer to be overwritten. Reachability requires local System-level execution privileges, and the documented consequence is service interruption rather than code execution.
Summary
What happened
Out-of-bounds write in modem control code on UNISOC Android 10 chipsets allows local users to interrupt service via unspecified vectors. The modem control device performs a write without the required bounds check, allowing memory outside the intended buffer to be overwritten. Reachability requires local System-level execution privileges, and the documented consequence is service interruption rather than code execution.
The record
- CVE
- CVE-2022-48380
- Published
- May 9, 2023
- Updated
- Jan 28, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-787
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- May 9, 2023CVE publishedPublication date reported by the CVE source.
- Jan 28, 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