CVE-2016-11035
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedAn issue was discovered on Samsung mobile devices with software through 2016-05-27 (Exynos AP chipsets). A local graphics user can cause a Kernel Crash via the fb0(DECON) frame buffer interface. The Samsung ID is SVE-2016-7011 (October 2016).
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceA local graphics user can trigger a kernel crash via the fb0 (DECON) frame buffer interface on Samsung mobile devices with Exynos AP chipsets running software through May 2016. This is a local denial-of-service vulnerability where the DECON framebuffer driver fails to properly validate or handle certain graphics user operations, leading to a kernel panic.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE dataall versionsCVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify device chipset architectureCheck if the Samsung mobile device uses an Exynos AP chipset (this information is typically available via device specifications, /proc/cpuinfo, or diagnostic utilities)Affected if The device does NOT use an Exynos chipset - this vulnerability only affects Exynos-based Samsung devices
-
Verify the DECON framebuffer interface existsCheck for the presence of /dev/fb0 or fb0 in /sys/class/graphics/ which indicates the DECON framebuffer driver is loaded and activeAffected if The fb0 (DECON) framebuffer interface is present and accessible to graphics users
-
Determine firmware/software versionCheck the Android build date or firmware version on the Samsung Exynos device (available in Settings > About Phone > Build number or via getprop ro.build.date.utc)Affected if The firmware was released on or before May 2016 and has not received the October 2016 security update (SVE-2016-7011)
-
Confirm unpatched kernel driverIf accessible, check the kernel version and DECON driver version against the patched version included in the October 2016 Samsung security updateAffected if The kernel driver remains unpatched and the October 2016 Samsung security patch (SVE-2016-7011) has not been applied
A user is affected if they have a Samsung device with an Exynos chipset running firmware from May 2016 or earlier that still contains the vulnerable DECON framebuffer driver and has not received the October 2016 security update.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataApply the October 2016 Samsung security update (SVE-2016-7011) which patches the DECON framebuffer driver vulnerability. Users should update their device firmware to a version containing this security patch.
- Consultation2.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,480.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-11035 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2016-11035 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data