CVE-2025-20071
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 · uneditedNULL pointer dereference for some Intel(R) Graphics Drivers 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 confidenceA NULL pointer dereference vulnerability in Intel(R) Graphics Drivers allows an authenticated user with local access to potentially cause a denial of service condition.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- Changed
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/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.
-
Identify Intel Graphics Driver installationCheck for Intel Graphics Drivers via system device manager or driver enumeration tools (e.g., 'dxdiag' on Windows, 'lspci -v' or 'lsmod' on Linux). Look for Intel GPU entries under display adapters.Affected if No Intel Graphics Driver is found, the system is not affected because the vulnerable component is not present.
-
Retrieve installed Intel Graphics Driver versionUse Intel Driver & Support Assistant, or check the driver file properties on the igfx*.sys driver file in the System32/drivers folder (Windows), or run 'cat /proc/driver/intel_version' or check the kernel module version on Linux.Affected if The installed version cannot be determined or is older than any recent Intel graphics driver release, indicating potential vulnerability.
-
Confirm the graphics driver is actively loadedVerify the Intel GPU driver is loaded and active. On Windows, check Device Manager for 'Enabled' status. On Linux, run 'lsmod | grep intel' or check /sys/class/drm for Intel GPU entries.Affected if The Intel Graphics Driver is not loaded or not enabled, the specific vulnerability condition is not reachable.
-
Verify local authenticated access existsConfirm user account presence on the system. This vulnerability requires an authenticated user session. Check if standard user or administrator accounts exist and can log in locally.Affected if The system has no local user accounts or disables local logins, exploitation is not possible.
The environment is affected if Intel Graphics Drivers are installed, the driver version is present and can be compared against fixed releases, and the system allows local authenticated access which enables the vulnerable code path.
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 dataUpdate Intel Graphics Drivers to the latest version provided by Intel through their official support channels or system patch management.
- Consultation1.0 h
- Implementation2.0 h
- Testing2.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,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-20071 — 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-2025-20071 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