CVE-2017-18301
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 · uneditedIn Small Cell SoC and Snapdragon (Automobile, Mobile, Wear) in version FSM9055, FSM9955, MDM9607, MDM9640, MDM9650, MSM8909W, SD 425, SD 427, SD 430, SD 435, SD 450, SD 617, SD 625, SD 650/52, SD 820, SD 820A, SD 835, SD 845, SDM630, SDM636, SDM660, SDX20, Snapdragon_High_Med_2016, providing the NULL argument of ICE regulator while processing create key IOCTL results in system restart.
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 confidenceA NULL pointer dereference vulnerability in the ICE (Inline Crypto Engine) regulator driver allows an attacker to cause a system restart by passing a NULL argument during the create key IOCTL operation on affected Snapdragon and Small Cell SoC hardware. This is a denial-of-service vulnerability affecting the kernel driver level.
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 versionsall versionsall versionsall versionsall versionsall versionsall versionsall 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.0/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 the Qualcomm chipset modelCheck the system hardware or boot logs for the chipset identifier (e.g., Fsm9055, Fsm9955, Mdm9607, Mdm9640, Mdm9650, Msm8909w, Sd425, Sd427)Affected if The chipset matches any of the affected models listed in the CVE
-
Check the firmware versionRetrieve the firmware version from the device system information or boot logs and compare against the CVE affected versionsAffected if The firmware version is among the listed affected products (all versions of Fsm9055, Fsm9955, Mdm9607, Mdm9640, Mdm9650, Msm8909w, Sd425, Sd427)
-
Verify the ICE driver is presentCheck for the presence of the ICE (Inline Crypto Engine) regulator driver in the kernel module list or /proc/modulesAffected if The ICE driver module is loaded on the system
-
Check for IOCTL interface accessibilityInspect /dev or /sys for crypto-related device nodes that handle the create key IOCTL operation, and verify if unprivileged access is possibleAffected if The ICE driver IOCTL interface for key creation is accessible and accepts user-supplied arguments
A system is affected if it runs on any of the listed Qualcomm chipsets (Fsm9055, Fsm9955, Mdm9607, Mdm9640, Mdm9650, Msm8909w, Sd425, Sd427) with any firmware version and has the ICE driver loaded with an accessible IOCTL interface for the create key operation.
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 Qualcomm vendor firmware/security updates for affected chipsets. If a patch is unavailable, implement input validation in the IOCTL handler to reject NULL arguments before passing them to the ICE regulator.
- Consultation2.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 $2,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-18301 — 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-18301 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