CVE-2018-3611
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 · uneditedBounds check vulnerability in User Mode Driver in Intel Graphics Driver 15.40.x.4 and 21.20.x.x allows unprivileged user to cause a denial of service via local access.
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 bounds check vulnerability exists in the User Mode Driver component of Intel Graphics Driver versions 15.40.x.4 and 21.20.x.x. The flaw allows an unprivileged local user to trigger a denial of service condition due to insufficient bounds checking in the driver's user-mode component.
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<= 15.40.37.4835<= 20.19.15.4835CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.0/AV:N/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 if Intel Graphics Driver is installedOpen Device Manager, expand 'Display adapters' to see if an Intel graphics device is listed. Alternatively, check 'Programs and Features' for Intel Graphics Driver entries.Affected if No Intel graphics driver is present on the system, then the vulnerability does not apply.
-
Retrieve the installed Intel Graphics Driver versionIn Device Manager, right-click the Intel graphics device, select Properties, go to the Driver tab, and note the Driver Version field. Alternatively, run 'dxdiag' from the command prompt and check the Display tab for Driver Version.Affected if Unable to determine the driver version means the check is inconclusive.
-
Compare installed version against affected rangesCompare the retrieved driver version number to the affected ranges: versions <= 15.40.37.4835 and versions <= 20.19.15.4835. Note that versions 15.40.x.4 through 15.40.37.4835 and 20.19.x.x through 20.19.15.4835 are affected.Affected if The installed version falls within or below these version ranges, meaning the system is running a vulnerable driver version.
-
Verify the User Mode Driver component is presentCheck if the Intel Graphics User Mode Driver is loaded. On Windows, this typically appears as a loaded driver in the output of 'driverquery' command or can be verified through the Intel Graphics Control Panel under driver information.Affected if The User Mode Driver component must be present and loaded for the vulnerability to be exploitable; if only a kernel-mode or basic driver is present without the user-mode component, the specific flaw may not apply.
A system is affected if it has Intel Graphics Driver installed with a version number at or below 15.40.37.4835 or at or below 20.19.15.4835, and the User Mode Driver component is present and active.
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 dataUpdate Intel Graphics Driver to a patched version provided by Intel through their official driver download channels, or apply security updates delivered via operating system update mechanisms.
- Consultation1.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-3611 — 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-2018-3611 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