I915 GraphicsApplication · Intel
CVE-2023-28410
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 · uneditedImproper restriction of operations within the bounds of a memory buffer in some Intel(R) i915 Graphics drivers for linux before kernel version 6.2.10 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 confidenceA buffer boundary vulnerability in the Intel i915 Graphics driver for Linux kernels prior to 6.2.10 allows a locally authenticated user to potentially perform out-of-bounds memory operations leading to privilege escalation.
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
I915 GraphicsApplication
< 6.2.10CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Check the running Linux kernel versionRun `uname -r` or `cat /proc/version` to display the kernel versionAffected if The kernel version is earlier than 6.2.10 (e.g., 6.2.9 or lower)
-
Verify the i915 graphics driver is loadedRun `lsmod | grep i915` to list loaded i915 kernel modulesAffected if The i915 module is loaded and the kernel version is below 6.2.10
-
Confirm Intel graphics hardware is presentRun `lspci | grep -i vga` or `lspci | grep -i graphics` to list graphics devicesAffected if Intel graphics hardware is detected and the kernel version is below 6.2.10
A system is affected if it runs a Linux kernel version earlier than 6.2.10 with the Intel i915 graphics driver loaded and Intel graphics hardware present.
Generated from the published advisory. Verify against your own configuration.
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 · scoped6.2.10
Upgrade the Linux kernel to version 6.2.10 or later, or apply the vendor-supplied patch to the i915 driver for the specific kernel version in use.
Linux kernel 6.2.10 or later
- Identify the current running kernel version using 'uname -r'
- Back up critical data and create a system snapshot or backup as a precaution
- For Debian/Ubuntu-based systems: Run 'sudo apt update' then 'sudo apt upgrade' or install specific kernel package using 'sudo apt install linux-image-6.2.10-*'
- For RHEL/CentOS/Fedora-based systems: Run 'sudo yum update kernel' or 'sudo dnf update kernel'
- For other distributions: Obtain kernel 6.2.10 or later from distribution repositories or kernel.org, then install using distribution-specific package manager or compile from source
- Update bootloader configuration if necessary (GRUB will typically auto-detect)
- Reboot the system using 'sudo reboot'
- Verify the fix by checking the kernel version with 'uname -r' - it should show 6.2.10 or later
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in I915 Graphics
Scoped from the published advisory
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-28410 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-28410 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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