Local service interruption via unchecked memory write
Published May 9, 2023 · Updated Jan 28, 2025
An out-of-bounds write in the UNISOC Android 10 modem control device allows local users to interrupt service through memory corruption. The kernel component writes beyond a destination buffer because the modem control path omits a bounds check; the exact input and function are undisclosed. System execution privileges are required, and the documented consequence is local service interruption on the listed chipsets.
Summary
What happened
An out-of-bounds write in the UNISOC Android 10 modem control device allows local users to interrupt service through memory corruption. The kernel component writes beyond a destination buffer because the modem control path omits a bounds check; the exact input and function are undisclosed. System execution privileges are required, and the documented consequence is local service interruption on the listed chipsets.
The record
- CVE
- CVE-2022-48381
- Published
- May 9, 2023
- Updated
- Jan 28, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-787, CWE-400, T1499
- 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