dbcve.org
Improper Access ControlWeakness · CWE-284

CVE-2024-45371

MEDIUM · 6.7 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 →
67/100
Remediation priority · Elevated

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) Arc™ & Iris(R) Xe graphics software before version 32.0.101.6077 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 · high confidence

Improper access control vulnerability in Intel Arc and Iris Xe graphics software allows an authenticated local user to potentially cause a denial of service. The vulnerability exists in versions prior to 32.0.101.6077 and stems from insufficient access control checks within the graphics software component.

MitigationUpdate Intel Arc and Iris Xe graphics software to version 32.0.101.6077 or later to remediate the improper access control vulnerability.

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
Required
Scope
Changed
Confidentiality
None
Integrity
Low
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:R/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 hardware
    Check system for Intel Arc or Iris Xe GPU using 'lspci | grep -i vga' on Linux or Device Manager on Windows. Look for entries containing 'Intel' and 'Arc' or 'Xe' in the device name.
    Affected if No Intel Arc or Iris Xe GPU is present in the system (different GPU vendors are not affected by this specific Intel vulnerability)
  2. Determine installed graphics driver version
    On Windows: Open Device Manager, expand Display adapters, right-click Intel GPU, select Properties, view Driver version. On Linux: Run 'cat /sys/class/drm/card0/device/driver' or check '/usr/bin/intel_gpu_top' if installed. Intel utilities like 'Intel Driver & Support Assistant' may also report the version.
    Affected if Unable to retrieve a version number for Intel graphics software (the vulnerability only applies to Intel's specific graphics driver/software)
  3. Compare version against vulnerable range
    Compare the installed version number to the affected range: any version prior to 32.0.101.6077 is vulnerable. Version 32.0.101.6077 and later are patched.
    Affected if Installed Intel graphics driver version is below 32.0.101.6077 (for example, 32.0.101.5551 or 31.0.101.xxxx series)
  4. Verify local user access exists
    Check whether untrusted or lower-privilege local user accounts exist on the system using 'who' or 'net user' commands. The vulnerability requires an authenticated local user to exploit the improper access control.
    Affected if The system has multiple user accounts and the graphics software component is accessible to non-administrative local users (the flaw allows a local authenticated user to cause denial of service)
  5. Confirm graphics software component is active
    Verify the Intel graphics driver/runtime is loaded and active. On Windows, check if Intel graphics control panel is accessible. On Linux, verify 'i915' kernel module is loaded via 'lsmod | grep i915' or 'systemctl status' for graphics-related services.
    Affected if Intel graphics software is disabled, not installed, or the driver is not loaded (the vulnerability cannot be exploited if the affected component is not present or active)

The environment is affected if the system contains Intel Arc or Iris Xe graphics hardware with an installed driver version prior to 32.0.101.6077, and the graphics software component is active and accessible to local authenticated users.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update Intel Arc and Iris Xe graphics software to version 32.0.101.6077 or later to remediate the improper access control vulnerability.

Recommended fix High confidence

32.0.101.6077

  1. 1. Identify the current Intel Graphics Driver version installed on the system (via Device Manager or Intel Driver & Support Assistant)
  2. 2. Navigate to Intel's official support website or download center
  3. 3. Download Intel Graphics Driver version 32.0.101.6077 or later for Intel Arc/Iris Xe graphics
  4. 4. Run the installer and follow the on-screen prompts to update the graphics driver
  5. 5. Restart the system to complete the driver installation
  6. 6. Verify the installed driver version is 32.0.101.6077 or later

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
4.0 hours of engineering $750
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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