dbcve.org
Graphics DriverApplication · Intel

CVE-2019-11111

HIGH · 7.8 CVSS v3.1 Published 2019-11-14
Fix available
A fix is available. Upgrade to 15.36.37.5074 or later.
See remediation →
80/100
Remediation priority · High
Zero-click

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 · unedited
Pointer corruption in the Unified Shader Compiler in Intel(R) Graphics Drivers before 10.18.14.5074 (aka 15.36.x.5074) may allow an authenticated user to potentially enable escalation of privilege 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 · moderate confidence

Pointer corruption vulnerability in the Unified Shader Compiler of Intel Graphics Drivers allows an authenticated local user to potentially escalate privileges. The vulnerability exists in driver versions prior to 10.18.14.5074 (15.36.x.5074).

MitigationUpdate Intel Graphics Drivers to version 10.18.14.5074 or later. Apply operating system security patches and ensure least-privilege principles to limit local access exposure.

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
Graphics DriverApplication
Affected:< 15.36.37.5074
Cloud BackupApplication
Affected:all versions
Data Availability ServicesApplication
Affected:all versions
Steelstore Cloud Integrated StorageApplication
Affected:all versions
Solidfire Baseboard Management Controller FirmwareOperating system
Affected:all versions

CVSS 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
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify Intel Graphics Driver installation
    On Windows, open Device Manager, expand 'Display adapters', and note the Intel driver name. On Linux, run 'lspci | grep VGA' or check /usr/share/X11/xorg.conf.d/ for Intel graphics. For the version, on Windows right-click the driver, select Properties, then the Driver tab. On Linux, run 'cat /proc/driver/intel_version' or 'intel_gpu_top' if installed.
    Affected if Intel Graphics Driver is present on the system
  2. Determine Intel Graphics Driver version number
    On Windows: In Device Manager driver properties, read the 'Driver Version' field (format like xx.xx.xx.xxxx). On Linux: Check 'cat /proc/driver/intel_version' or use 'dkms status' for installed graphics driver packages.
    Affected if A specific four-part version number is displayed (for example, 15.36.14.1234)
  3. Compare driver version to affected range
    Compare the installed version number to 15.36.37.5074. If the first three number groups (15.36.x) are lower, or if 15.36.37 is present but the fourth group is below 5074, the driver is vulnerable.
    Affected if Installed version is less than 15.36.37.5074 (for example, 15.36.14.1234 or 15.36.37.5073 would be affected)
  4. Check for NetApp product installations
    On systems running NetApp software, identify installed products by checking installed packages, services, or application listings. For NetApp Cloud Backup, look for 'cloudbackup' or related service names. For Data Availability Services, check for 'data_availability' services. For Steelstore, look for 'steelstore' processes. For Solidfire BMC, this is firmware-based and requires checking the BMC web interface or IPMI firmware version.
    Affected if Any NetApp Cloud Backup, Data Availability Services, Steelstore Cloud Integrated Storage, or Solidfire BMC is installed (all versions are affected per the CVE scope)

Your environment is affected if Intel Graphics Driver version is below 15.36.37.5074, or if any NetApp product listed (Cloud Backup, Data Availability Services, Steelstore, or Solidfire BMC) is installed regardless of version.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Upgrade available Upgrade to 15.36.37.5074 or later
Fixed in 15.36.37.5074
Interim mitigation

Update Intel Graphics Drivers to version 10.18.14.5074 or later. Apply operating system security patches and ensure least-privilege principles to limit local access exposure.

Fix this in Graphics Driver Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,390
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-11111 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2019-11111 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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