Remote device crash via UBSan hard abort
Published Jun 1, 2026 · Updated Jun 1, 2026
Integer overflow in Android 14, 15, 16, and 16-qpr2 allows remote authenticated users to crash devices through UBSan runtime handlers. The dng_sdk build previously linked UBSan's minimal runtime, whose arithmetic-overflow handlers abort execution; the patch replaces them with exceptions. A low-privileged remote context can trigger the failure without user interaction, interrupting availability without reported data exposure or modification.
Summary
What happened
Integer overflow in Android 14, 15, 16, and 16-qpr2 allows remote authenticated users to crash devices through UBSan runtime handlers. The dng_sdk build previously linked UBSan's minimal runtime, whose arithmetic-overflow handlers abort execution; the patch replaces them with exceptions. A low-privileged remote context can trigger the failure without user interaction, interrupting availability without reported data exposure or modification.
The record
- CVE
- CVE-2026-0040
- Published
- Jun 1, 2026
- Updated
- Jun 1, 2026
- Vendor
- Go standard library
- Product
- Android
- Classifications
- CWE-190, T1499.004
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 1, 2026CVE publishedPublication date reported by the CVE source.
- Jun 1, 2026Record 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=14
- Affected versionversion=15
- Affected versionversion=16
- Affected versionversion=16-qpr2
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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