dbcve.org
Graphics DriverApplication · Intel

CVE-2019-11112

HIGH · 7.8 CVSS v3.1 Published 2019-11-14
Fix available
A fix is available. Upgrade to 15.45.5077 / 26.20.100.6812 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
Memory corruption in Kernel Mode Driver in Intel(R) Graphics Driver before 26.20.100.6813 (DCH) or 26.20.100.6812 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 · high confidence

Memory corruption vulnerability in the Intel Graphics Kernel Mode Driver allows an authenticated local user to potentially escalate privileges. The flaw exists in driver versions prior to 26.20.100.6813 (DCH) or 26.20.100.6812, where improper memory handling in the kernel-mode component can be exploited to gain elevated privileges.

MitigationUpdate Intel Graphics Driver to version 26.20.100.6813 (DCH) or 26.20.100.6812 or later to patch the memory corruption vulnerability.

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.45.5077>= 24.20.100.6025, < 26.20.100.6812
Cloud BackupApplication
Affected:all versions
Data Availability ServicesApplication
Affected:all versions
Steelstore Cloud Integrated StorageApplication
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. Check Intel Graphics Driver version via PowerShell
    Run 'Get-WmiObject Win32_PnPSignedDriver | Where-Object {$_.DeviceName -like "*Intel*Graphics*"} | Select-Object DeviceName,DriverVersion,DriverDate' in PowerShell to list installed Intel graphics drivers and their versions
    Affected if The displayed DriverVersion falls within the affected ranges: less than 15.45.5077, or greater than or equal to 24.20.100.6025 but less than 26.20.100.6812 (or 26.20.100.6813 for DCH versions)
  2. Verify kernel-mode graphics driver is loaded
    Check if the Intel graphics kernel-mode driver (igdkmd64.sys) is loaded by running 'Get-Process | Where-Object {$_.ProcessName -like "*igfx*"}' or checking 'sc query igdkmd64' in Command Prompt
    Affected if The driver is actively loaded and its version matches the affected version ranges from step 1
  3. Check for NetApp Cloud Backup installation
    Look for NetApp Cloud Backup by checking 'Add or Remove Programs' registry key at HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall or by searching for 'NetApp Cloud Backup' in Programs and Features
    Affected if NetApp Cloud Backup is installed (all versions are affected according to the CVE data)
  4. Check for NetApp Data Availability Services installation
    Look for NetApp Data Availability Services in Programs and Features or check registry at HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall for entries containing 'NetApp' and 'Data Availability'
    Affected if NetApp Data Availability Services is installed (all versions are affected)
  5. Check for NetApp Steelstore Cloud Integrated Storage installation
    Look for NetApp Steelstore in Programs and Features or search for 'Steelstore' in installed programs list
    Affected if NetApp Steelstore Cloud Integrated Storage is installed (all versions are affected)

Your system is affected if the Intel Graphics Driver version is below 15.45.5077, or between 24.20.100.6025 and 26.20.100.6811, OR if any of the NetApp products (Cloud Backup, Data Availability Services, or Steelstore) are installed.

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.45.5077 / 26.20.100.6812 or later
Fixed in 15.45.507726.20.100.6812
Interim mitigation

Update Intel Graphics Driver to version 26.20.100.6813 (DCH) or 26.20.100.6812 or later to patch the memory corruption vulnerability.

Fix this in Graphics Driver Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-11112 — 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-11112 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