CVE-2019-11089
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 · uneditedInsufficient input validation in Kernel Mode module for Intel(R) Graphics Driver before version 25.20.100.6519 may allow an authenticated user to potentially enable 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 confidenceInsufficient input validation in the Kernel Mode module of Intel(R) Graphics Driver before version 25.20.100.6519 allows an authenticated local user to potentially cause a denial of service via malformed input to the graphics driver kernel 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< 25.20.100.6519all 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.1/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.
-
Check if Intel Graphics Driver is installedOn Windows, open Device Manager and expand 'Display adapters' to see if an Intel graphics device is listed. On Linux, run 'lspci | grep -i vga' or check for Intel graphics kernel modules.Affected if An Intel graphics adapter/driver is present in the system
-
Identify the installed Intel Graphics Driver versionOn Windows, right-click the Intel graphics device in Device Manager, select Properties > Driver tab, and note the Driver Version. Alternatively, use Intel Driver & Support Assistant or check 'Programs and Features' for Intel Graphics Driver. On Linux, check /usr/share/X11/xorg.conf.d/ or use 'glxinfo' or check the kernel module version.Affected if A version number is found that is below 25.20.100.6519
-
Compare your driver version against the vulnerable rangeCompare the version number you found against 25.20.100.6519. Ensure you check all three version components (25.20.100) and the build number (6519). Intel driver versions follow a format like xx.xx.xxxx.xxxx.Affected if The installed version is any build before 25.20.100.6519 (for example, 25.20.100.6518, 25.20.100.6373, etc.)
-
Check for presence of affected NetApp productsOn systems running NetApp Cloud Backup, NetApp Data Availability Services, NetApp Steelstore Cloud Integrated Storage, or Netapp Solidfire Baseboard Management Controller Firmware, verify which of these products are installed using the NetApp support tools or checking installed software/packages.Affected if Any of these NetApp products are installed (all versions are affected per the advisory)
You are affected if Intel Graphics Driver version is below 25.20.100.6519, or if any of the listed NetApp products are installed on your system.
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 data25.20.100.6519
Update Intel Graphics Driver to version 25.20.100.6519 or later to remediate the vulnerability.
- Consultation1.0 h
- Implementation2.0 h
- Testing1.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,424.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-11089 — 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-2019-11089 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