dbcve.org
Graphics DriversApplication · Intel

CVE-2020-12371

MEDIUM · 5.5 CVSS v3.1 Published 2021-02-17
Fix available
A fix is available. Upgrade to 26.20.100.8141 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
Divide by zero in some Intel(R) Graphics Drivers before version 26.20.100.8141 may allow a privileged user to potentially enable 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 confidence

A divide-by-zero vulnerability exists in Intel Graphics Drivers for versions prior to 26.20.100.8141. The flaw can be triggered by a privileged user with local access, causing a denial of service condition.

MitigationUpdate Intel Graphics Drivers to version 26.20.100.8141 or later. Apply the vendor patch through standard driver update mechanisms or Intel's driver update utilities.

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 DriversApplication
Affected:< 26.20.100.8141

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. Verify Intel Graphics Drivers are installed
    Open Device Manager, expand 'Display adapters', and look for Intel integrated graphics devices (e.g., Intel UHD Graphics, Intel Iris Xe). If present, the system has Intel Graphics Drivers.
    Affected if No Intel Graphics Drivers are installed, this CVE does not apply.
  2. Retrieve the installed driver version
    In Device Manager, right-click the Intel Graphics device, select Properties, go to the Driver tab, and note the Driver Version field. Alternatively, run 'dxdiag' in the command prompt and check the Display tab for the driver version.
    Affected if Unable to determine driver version means the check cannot be completed.
  3. Compare against the vulnerable version threshold
    Compare the installed driver version (e.g., 26.20.100.7212) to the fixed version 26.20.100.8141. Version numbers follow major.minor.build.revision format - any version with the first three numbers lower than 26.20.100, or equal to 26.20.100 with a build number below 8141, is vulnerable.
    Affected if Installed version is less than 26.20.100.8141, the system is affected by this vulnerability.

The environment is affected if Intel Graphics Drivers are installed and the driver version is lower than 26.20.100.8141.

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.8141 or later
Fixed in 26.20.100.8141
Interim mitigation

Update Intel Graphics Drivers to version 26.20.100.8141 or later. Apply the vendor patch through standard driver update mechanisms or Intel's driver update utilities.

Fix this in Graphics Drivers 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-2020-12371 — 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-2020-12371 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