dbcve.org
Uncontrolled Search Path (DLL Hijack)Weakness · CWE-427

CVE-2024-46895

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
Uncontrolled search path for some Intel(R) Arc™ & Iris(R) Xe graphics software before version 32.0.101.6083/32.0.101.5736 may allow an authenticated user to potentially enable escalation of privilege 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

This is an uncontrolled search path vulnerability (likely DLL hijacking) in Intel Arc and Iris Xe graphics software. The software searches for required files in an insecure manner, allowing an authenticated local attacker to place malicious files that get loaded by the vulnerable software, enabling privilege escalation.

MitigationUpdate Intel Arc/Iris Xe graphics software to version 32.0.101.6083 or 32.0.101.5736 or later to resolve the uncontrolled search path issue.

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
High
Privileges
Low
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:H/PR:L/UI:R/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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify Intel Arc or Iris Xe graphics software is installed
    Open Settings > Apps & Features (Windows) or check /Applications (macOS), or run: 'Get-WmiObject -Class Win32_Product | Select-Object Name,Version' (PowerShell) or 'dpkg -l | grep -i intel' (Linux)
    Affected if Intel Arc Control, Iris Xe Graphics, or Intel Graphics Driver software appears in the installed programs list
  2. Identify the installed Intel graphics driver version
    Run 'dxdiag' (Windows) and check the Display tab, or run 'intel_gpu_top' (Linux), or check the driver details in Device Manager > Display adapters > Intel GPU > Properties > Driver tab
    Affected if A version number is displayed (for example: 31.0.101.xxxx or 32.0.101.xxxx series)
  3. Compare installed version against fixed releases
    Note the full version number from step 2. Compare numerically: the fixed versions are 32.0.101.6083 and 32.0.101.5736; any version below these in the 32.0.101.xxxx series is affected, as are earlier 31.0.x.xx versions
    Affected if The installed version is lower than 32.0.101.5736 (for example: 32.0.101.5592, 31.0.101.5002, or any 30.x.x.x release)
  4. Confirm the software uses untrusted DLL search paths
    Use Process Monitor (Windows) or ltrace/strace (Linux) to observe file loading behavior when launching Intel graphics software, or inspect the application manifest and DLL search order using 'dumpbin /dependents' or a similar tool
    Affected if The software loads DLLs from current working directory, user-writable locations, or paths outside the secure Windows system directory (System32)

A user is affected if Intel Arc or Iris Xe graphics software is installed with a version lower than 32.0.101.5736 and the software loads DLLs from insecure paths.

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/Iris Xe graphics software to version 32.0.101.6083 or 32.0.101.5736 or later to resolve the uncontrolled search path issue.

Recommended fix Moderate confidence

Intel Graphics Driver version 32.0.101.6083 or 32.0.101.5736

  1. Identify the current version of Intel(R) Arc™ or Iris(R) Xe graphics software installed on the system
  2. Navigate to the official Intel support or download page for Intel graphics drivers
  3. Download the latest Intel graphics driver version 32.0.101.6083 or 32.0.101.5736 (whichever is the current stable release for your system)
  4. Run the installer with administrator privileges
  5. Follow the on-screen prompts to complete the driver installation
  6. Restart the system when prompted to ensure the new driver loads correctly
  7. Verify the installed version matches the target fixed version

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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