Kernel crash via fb0(DECON) framebuffer interface
Published Apr 7, 2020 · Updated Aug 6, 2024
Kernel crash in Samsung mobile-device software through 2016-05-27 allows local users to interrupt service via the fb0(DECON) interface. Public Samsung and CVE materials identify the DECON framebuffer locus but do not disclose which input or memory operation triggers the crash. Access to the local graphics interface on an Exynos AP device is required, and the reported consequence is limited to a kernel crash.
Summary
What happened
Kernel crash in Samsung mobile-device software through 2016-05-27 allows local users to interrupt service via the fb0(DECON) interface. Public Samsung and CVE materials identify the DECON framebuffer locus but do not disclose which input or memory operation triggers the crash. Access to the local graphics interface on an Exynos AP device is required, and the reported consequence is limited to a kernel crash.
The record
- CVE
- CVE-2016-11035
- Published
- Apr 7, 2020
- Updated
- Aug 6, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-119, T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Apr 7, 2020CVE publishedPublication date reported by the CVE source.
- Aug 6, 2024Record 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