dbcve.org
Out-of-bounds ReadWeakness · CWE-125

CVE-2025-20101

HIGH · 8.4 CVSS v3.1 Published 2025-05-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
86/100
Remediation priority · High
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 for some Intel(R) Graphics Drivers may allow an authenticated user to potentially enable information disclosure or 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

An out-of-bounds read vulnerability exists in Intel(R) Graphics Drivers that allows an authenticated local user to access memory beyond allocated buffer boundaries. This can lead to information disclosure (reading sensitive memory contents) or denial of service (system instability/crash) via local access.

MitigationApply the latest Intel Graphics Driver updates from Intel's support website or through enterprise patch management channels. Prioritize systems with graphics driver exposure to untrusted local users.

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
High
Integrity
None
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/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. Confirm Intel Graphics Driver is installed
    On Windows: Open Device Manager, expand 'Display adapters', look for Intel GPU entries. On Linux: Run 'lspci | grep -i intel' or 'lsmod | grep i915' to list loaded graphics modules.
    Affected if No Intel GPU driver is listed in Device Manager or no i915 module is loaded, then the system is not affected by this specific vulnerability.
  2. Retrieve the installed Intel Graphics Driver version
    On Windows: Right-click the Intel GPU in Device Manager > Properties > Driver tab > Driver Version. Or run 'msinfo32' and check Components > Display. On Linux: Run 'modinfo i915 | grep version' or check '/sys/class/drm/card0/device/driver' version.
    Affected if The driver version cannot be determined or the system uses a third-party GPU driver instead of Intel's official driver.
  3. Compare driver version against affected releases
    Document the exact version number from Step 2. Intel's security advisory for CVE-2025-20101 lists specific driver version ranges as affected. Compare your version to those ranges.
    Affected if Your installed version falls within the range of affected versions listed in Intel's official CVE-2025-20101 advisory.
  4. Verify the graphics driver is actively loaded and in use
    On Windows: Confirm the Intel GPU is the active display adapter. On Linux: Check 'glxinfo | grep renderer' or run 'cat /proc/driver/nvidia/version' (substitute nvidia with intel) to confirm the driver is operational.
    Affected if The driver is present but not actively driving graphics output; the vulnerability would require an active connection to the graphics subsystem.
  5. Assess local user access exposure
    Review system access controls to determine if untrusted or low-privilege local users have authenticated access to the system. Check user group memberships and terminal access policies.
    Affected if Untrusted or low-privileged local users can log in to the system, as the vulnerability requires an authenticated local user session.

A system is affected if it runs an Intel Graphics Driver version within the affected range, has the driver actively loaded, and permits untrusted local users to authenticate to the system.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the latest Intel Graphics Driver updates from Intel's support website or through enterprise patch management channels. Prioritize systems with graphics driver exposure to untrusted local users.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing5.0 h
  • Review / QA3.0 h
17.0 hours of engineering $2,970
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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