dbcve.org
Iris Xe GraphicsApplication · Intel

CVE-2023-28404

MEDIUM · 5.5 CVSS v3.1 Published 2023-11-14
Fix available
A fix is available. Upgrade to 31.0.101.4255 or later.
See remediation →
57/100
Remediation priority · Elevated
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 in the Intel(R) Arc(TM) & Iris(R) Xe Graphics - WHQL - Windows drivers before version 31.0.101.4255 may allow an authenticated user to potentially enable information disclosure 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

Out-of-bounds read vulnerability in Intel Arc and Iris Xe Graphics Windows drivers before version 31.0.101.4255 allows an authenticated local user to potentially read sensitive information from memory beyond allocated buffer boundaries, leading to information disclosure.

MitigationUpdate Intel graphics drivers to version 31.0.101.4255 or later through Intel's driver update utilities or enterprise deployment tools.

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

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

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
    Open Device Manager, expand 'Display adapters' and look for 'Intel Iris Xe Graphics', 'Intel Arc A Series', or similar Intel GPU names. Alternatively, run 'dxdiag' in the command prompt and check the display information.
    Affected if The system does not have Intel Iris Xe Graphics or Intel Arc A Graphics hardware - if a different GPU (NVIDIA, AMD, older Intel) is present, this CVE does not apply.
  2. Find installed driver version via Device Manager
    In Device Manager, right-click the Intel graphics device, select 'Properties', go to the 'Driver' tab, and note the 'Driver Version' field. Compare the four-part version number to 31.0.101.4255.
    Affected if The driver version shown is less than 31.0.101.4255 (for example, 31.0.101.4092 or earlier).
  3. Find installed driver version via dxdiag
    Run 'dxdiag' from the command prompt, navigate to the 'Display' tab, and locate the 'Driver Version' and 'Driver Date' fields under the Intel graphics entry.
    Affected if The driver version displayed is a release earlier than 31.0.101.4255.
  4. Find driver version via Intel Graphics Command Center
    Open Intel Graphics Command Center, go to 'Drivers' section, and check the currently installed driver version displayed there.
    Affected if The version shown is lower than 31.0.101.4255.

A user is affected only if their system has Intel Iris Xe or Intel Arc A Graphics hardware AND the installed Windows driver version is earlier 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 deployment tools.

Recommended fix High confidence

31.0.101.4255

  1. Identify current Intel graphics driver version via Device Manager (Display adapters > Intel Iris Xe Graphics or Intel Arc A Graphics > Properties > Driver tab)
  2. Download Intel Graphics Driver version 31.0.101.4255 or later from intel.com support/downloads
  3. Run the Intel driver installer as Administrator
  4. Follow on-screen prompts to complete driver installation
  5. Restart the system to load the updated driver
  6. Verify the new driver version is installed by checking Device Manager again

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

Fix this in Iris Xe Graphics Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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