Local service interrupt via unchecked DRM driver write
Published Jan 18, 2024 · Updated Jun 20, 2025
An out-of-bounds write in the DRM driver for affected Unisoc chipsets on Android 11 through Android 13 allows local users to interrupt service. The driver performs a write without checking the destination bounds; Unisoc has not disclosed the affected function, input, or trigger path. Triggering the flaw requires System-level execution privileges, and no remote path or more specific denial-of-service behavior is reported.
Summary
What happened
An out-of-bounds write in the DRM driver for affected Unisoc chipsets on Android 11 through Android 13 allows local users to interrupt service. The driver performs a write without checking the destination bounds; Unisoc has not disclosed the affected function, input, or trigger path. Triggering the flaw requires System-level execution privileges, and no remote path or more specific denial-of-service behavior is reported.
The record
- CVE
- CVE-2023-48358
- Published
- Jan 18, 2024
- Updated
- Jun 20, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-787
- Attack vector
- local
- Privileges
- admin
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.
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