dbcve.org
Graphics DriverApplication · Intel

CVE-2019-14574

MEDIUM · 5.5 CVSS v3.1 Published 2019-11-14
Fix available
A fix is available. Upgrade to 26.20.100.7209 or later.
See remediation →
57/100
Remediation priority · Elevated
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
Out of bounds read in a subsystem for Intel(R) Graphics Driver versions before 26.20.100.7209 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 · moderate confidence

Out of bounds read vulnerability in Intel Graphics Driver (versions before 26.20.100.7209) allows an authenticated local user to trigger a denial of service condition. The vulnerability stems from improper bounds checking in a graphics driver subsystem, potentially causing the system to read memory outside allocated buffers when processing certain graphics operations.

MitigationApply Intel Graphics Driver version 26.20.100.7209 or later. For systems where immediate patching is not feasible, restrict local unprivileged access and monitor for anomalous graphics driver behavior.

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:< 26.20.100.7209
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
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 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 graphics driver listed. On Linux, run 'lspci | grep -i vga' or check /sys/class/drm for Intel GPU detection.
    Affected if No Intel GPU driver is found, the system uses a different GPU vendor, or the driver is not the Intel Graphics Driver.
  2. Retrieve the installed Intel Graphics Driver version
    On Windows, open Device Manager, right-click the Intel GPU, select Properties, go to the Driver tab, and note the Driver Version. Alternatively, run 'driverquery /v | findstr i915' or check the registry at HKLM\SYSTEM\CurrentControlSet\Services\iaLPSSi_VEN_8086. On Linux, run 'cat /sys/class/drm/card0/device/driver/version' or use 'dmesg | grep -i intel' for driver load information.
    Affected if Unable to determine the Intel Graphics Driver version from the system.
  3. Compare the installed version against the vulnerable range
    Compare the retrieved driver version to 26.20.100.7209. Versions below 26.20.100.7209 are affected. Note that version numbering may vary by Windows version; check the full version string including the build component.
    Affected if The installed Intel Graphics Driver version is numerically less than 26.20.100.7209 (for example, 26.20.100.7153, 26.20.100.7000, or earlier).
  4. Verify local authenticated access context
    Confirm that the vulnerability requires an authenticated local user. Check if unprivileged local user accounts exist on the system using 'net user' or Local Users and Groups (lusrmgr.msc).
    Affected if The system permits local user accounts and the vulnerable driver version is present.

The system is affected if Intel Graphics Driver version 26.20.100.7209 or higher is not installed and the system contains an Intel GPU with the vulnerable driver version loaded.

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 26.20.100.7209 or later
Fixed in 26.20.100.7209
Interim mitigation

Apply Intel Graphics Driver version 26.20.100.7209 or later. For systems where immediate patching is not feasible, restrict local unprivileged access and monitor for anomalous graphics driver behavior.

Fix this in Graphics Driver Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing4.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,900
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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