CVE-2017-18693
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 KK(4.4), L(5.0/5.1), M(6.0), and N(7.0) software. There is a buffer overflow in the fps sysfs entry. The Samsung ID is SVE-2016-7510 (January 2017).
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 · moderate confidenceBuffer overflow vulnerability in the fps sysfs entry on Samsung mobile devices running Android KK(4.4) through N(7.0). The overflow occurs in a kernel sysfs interface, potentially allowing local privilege escalation or denial of service.
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 data= 4.4= 5.0= 5.1= 6.0= 7.0CVSS 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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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 manufacturerCheck if the device is a Samsung mobile device by reviewing device settings or system informationAffected if Device is not a Samsung mobile device (this CVE specifically affects Samsung devices)
-
Check Android versionNavigate to Settings > About Phone > Android version, or run 'getprop ro.build.version.release' in a shellAffected if Android version is NOT 4.4, 5.0, 5.1, 6.0, or 7.0 (only these specific versions are affected)
-
Locate fps sysfs entryList contents of /sys/class/graphics/ directory to find fps-related entries, typically under fb0/fpsAffected if The fps sysfs entry does not exist on the device (vulnerability only applies when this interface is present)
-
Verify kernel sysfs write accessCheck file permissions on the fps entry using 'ls -la /sys/class/graphics/fb0/fps' if it existsAffected if The fps entry is world-writable or group-writable without appropriate restrictions
A device is affected if it is a Samsung mobile device running Android 4.4, 5.0, 5.1, 6.0, or 7.0 with a writable fps sysfs interface present in the kernel.
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 dataThis Samsung firmware-level vulnerability requires vendor security updates. Organizations should ensure affected devices receive Samsung patches, implement network segmentation, and restrict physical access to mitigate local exploitation vectors.
- Consultation4.0 h
- Implementation16.0 h
- Testing10.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $9,440.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-18693 — 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-2017-18693 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