dbcve.org
Iris Xe GraphicsApplication · Intel

CVE-2023-28401

HIGH · 7.8 CVSS v3.1 Published 2023-11-14
Fix available
A fix is available. Upgrade to 31.0.101.4255 or later.
See remediation →
80/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 write in some Intel(R) Arc(TM) & Iris(R) Xe Graphics - WHQL - Windows drivers before version 31.0.101.4255 may allow 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 · moderate confidence

Out-of-bounds write vulnerability in Intel Arc and Iris Xe Graphics Windows WHQL drivers before version 31.0.101.4255 allows an authenticated local user to potentially execute code with elevated privileges due to improper bounds checking in the graphics driver.

MitigationUpdate Intel graphics drivers to version 31.0.101.4255 or later through Intel's driver update utilities or enterprise patch management systems.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Iris Xe GraphicsApplication
Affected:< 31.0.101.4255
Arc A GraphicsApplication
Affected:< 31.0.101.4255

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
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/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. Check Intel graphics driver version via Device Manager
    Open Device Manager, expand 'Display adapters', right-click on 'Intel Iris Xe Graphics' or 'Intel Arc A Series Graphics', select Properties, go to the Driver tab, and note the Driver Version field
    Affected if The displayed version number is lower than 31.0.101.4255
  2. Check Intel graphics driver version via command line
    Open Command Prompt or PowerShell and run: wmic path win32_VideoController get name,driverversion
    Affected if The driverversion shown for Intel Iris Xe Graphics or Intel Arc A Graphics is below 31.0.101.4255
  3. Check Intel graphics driver version via registry
    Open Registry Editor and navigate to HKLM\SYSTEM\CurrentControlSet\Control\Class\{4d36e968-e325-11ce-bfc1-08002be10318}\0000, then look for the DriverVersion value in the right pane
    Affected if The DriverVersion registry value is a version string lower than 31.0.101.4255
  4. Verify the specific graphics product
    Confirm the system has either Intel Iris Xe Graphics or Intel Arc A Series Graphics by checking Device Manager or the wmic output under the name field
    Affected if The system has an affected Intel GPU product (Iris Xe or Arc A) and the driver version is below 31.0.101.4255

A user is affected if their Windows system has Intel Iris Xe Graphics or Intel Arc A Graphics installed with a driver version lower than 31.0.101.4255.

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
Upgrade available Upgrade to 31.0.101.4255 or later
Fixed in 31.0.101.4255
Interim mitigation

Update Intel graphics drivers to version 31.0.101.4255 or later through Intel's driver update utilities or enterprise patch management systems.

Recommended fix High confidence

31.0.101.4255 or later

  1. Identify the current Intel Iris Xe Graphics or Arc A Graphics driver version installed on the system via Device Manager
  2. Navigate to Device Manager > Display adapters > Intel Iris Xe Graphics (or Intel Arc A Graphics)
  3. Right-click and select 'Update driver'
  4. Choose 'Search automatically for drivers' or download the latest driver from Intel's official support website
  5. Alternatively, visit Intel's download center at https://www.intel.com/content/www/us/en/support/ and search for your specific graphics product
  6. Download driver version 31.0.101.4255 or later for your specific graphics product and Windows version
  7. Run the downloaded installer and follow the on-screen prompts to complete the driver update
  8. Restart the system when prompted to ensure the new driver is properly loaded

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

Fix this in Iris Xe Graphics Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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