dbcve.org
Improper Access ControlWeakness · CWE-284

CVE-2025-20052

HIGH · 7.3 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 →
75/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
Improper access control for some Intel(R) Graphics software 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

Intel Graphics software contains an improper access control vulnerability that allows an authenticated local user to potentially cause a denial of service condition. The vulnerability stems from insufficient access control checks within the graphics software components, enabling a local attacker with valid credentials to exploit the weakness.

MitigationApply the latest Intel Graphics software updates or security patches provided by Intel for affected versions. Verify that the patch does not introduce regressions in graphics functionality.

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
Low
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:N/I:L/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 and expand 'Display adapters' to find Intel graphics devices, then right-click and select 'Properties' > 'Driver' to view the driver version. On Linux, run 'lspci | grep -i vga' or 'intel_gpu_top' if available to identify the driver and version. On macOS, check System Report > Graphics/Displays.
    Affected if Intel Graphics Driver is present on the system, making the software component potentially vulnerable.
  2. Retrieve exact driver version number
    On Windows: note the 'Driver Version' field in Device Manager. On Linux: run 'cat /sys/class/drm/card0/device/driver_version' or check 'lsmod | grep i915'. Record the full version string (for example, 31.0.101.xxxx or similar format used by Intel).
    Affected if A version number is found, allowing comparison to Intel's published affected version ranges.
  3. Check Intel security advisories for affected versions
    Search Intel's security advisories or Intel Product Security Center for CVE-2025-20052 to obtain the specific version ranges Intel has published as affected. Compare your retrieved version against this list.
    Affected if Your installed version falls within the version range Intel has listed as affected for this CVE.
  4. Verify local user authentication is possible
    Confirm that local user accounts exist on the system. On Windows: check 'Computer Management' > 'Local Users and Groups' > 'Users'. On Linux: check '/etc/passwd' or run 'getent passwd'. The vulnerability requires an authenticated local user.
    Affected if Local user accounts exist on the system, meaning an authenticated attacker could potentially attempt exploitation.
  5. Check graphics service accessibility
    On Windows: verify the Intel Graphics service (typically 'Intel(R) Graphics Control Panel' or 'igfxCUIService') is running. On Linux: check if i915 or other Intel graphics kernel modules are loaded via 'lsmod | grep i915'. The vulnerability exists within these graphics components.
    Affected if Intel graphics services or kernel modules are active, indicating the vulnerable component is running.

You are affected if Intel Graphics Driver is installed with a version that falls within the range Intel has published as vulnerable to CVE-2025-20052, and your system has local user accounts that could serve as authenticated attackers.

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 software updates or security patches provided by Intel for affected versions. Verify that the patch does not introduce regressions in graphics functionality.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,210
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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