CVE-2020-12373
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 · uneditedExpired pointer dereference 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 · moderate confidenceExpired pointer dereference vulnerability in Intel Graphics Drivers before version 26.20.100.8141 allows a privileged user to potentially cause a denial of service via local access. The vulnerability involves a dangling pointer that is dereferenced after being freed, likely due to improper memory management in the graphics driver.
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< 2.47CVSS 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
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:H/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 checksWork through these to decide whether this CVE applies to you.
-
Identify Intel Graphics Driver versionOpen Device Manager, expand 'Display adapters', right-click the Intel graphics device, select 'Properties', go to the 'Driver' tab, and note the Driver Version field. Alternatively, run 'dxdiag' in the Run dialog and check the 'Display' tab for the driver version.Affected if The installed driver version is earlier than 26.20.100.8141
-
Verify the graphics driver is loaded and activeOpen Task Manager, go to the 'Details' tab, look for igdkmd64.sys or similar Intel graphics kernel driver processes. Alternatively, check System Information (msinfo32) under Components > Display for active graphics driver information.Affected if An Intel graphics driver is actively loaded and its version is below 26.20.100.8141
-
Check for Intel Graphics Control PanelRight-click on the desktop and look for 'Intel Graphics Settings' or 'Intel Graphics Control Panel' in the context menu. Also check Programs and Features for installed Intel graphics software.Affected if Intel graphics software is installed and the driver version is below 26.20.100.8141
-
Confirm privilege contextThis vulnerability requires a privileged user. Check if the user checking this system has administrative or elevated privileges by examining User Account Control settings or running 'whoami /groups' in Command Prompt.Affected if A privileged user is operating on a system with an affected Intel graphics driver version below 26.20.100.8141
A system is affected if it has an Intel Graphics Driver installed with a version number lower than 26.20.100.8141 and the driver is actively loaded.
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 data2.47
Update Intel Graphics Drivers to version 26.20.100.8141 or later to remediate the vulnerability. Organizations should deploy the updated driver through their standard patch management processes and verify functionality post-update.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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 $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-12373 — 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-2020-12373 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