Local system crash via null pointer dereference
Published Jun 3, 2025 · Updated Jun 3, 2025
A null pointer dereference in the cplog service on affected UNISOC chipsets running Android 13 through 15 allows local users to crash the system. UNISOC has not disclosed the cplog code path that accepts the trigger or identified which pointer becomes null before dereference. No additional execution privileges or user interaction are required, and the documented consequence is a local system crash.
Summary
What happened
A null pointer dereference in the cplog service on affected UNISOC chipsets running Android 13 through 15 allows local users to crash the system. UNISOC has not disclosed the cplog code path that accepts the trigger or identified which pointer becomes null before dereference. No additional execution privileges or user interaction are required, and the documented consequence is a local system crash.
The record
- CVE
- CVE-2025-31711
- Published
- Jun 3, 2025
- Updated
- Jun 3, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-476, T1499
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 3, 2025CVE publishedPublication date reported by the CVE source.
- Jun 3, 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