From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-89822: drm/i915: Guard against NULL driver_data in i915_pci_probe()
Date: Wed, 16 Sep 2026 11:29:12 +0100 [thread overview]
Message-ID: <2026091601-CVE-2026-89822-e708@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
drm/i915: Guard against NULL driver_data in i915_pci_probe()
pci_match_device() can return the dummy pci_device_id_any entry
when a device is force-bound via sysfs driver_override, in which
case ->driver_data is unset (NULL). i915_pci_probe() casts it to
struct intel_device_info * unconditionally and dereferences
intel_info->require_force_probe, causing a NULL-ptr-deref.
(cherry picked from commit 2727922084672cc274ecea726ea00363c2893731)
The Linux kernel CVE team has assigned CVE-2026-89822 to this issue.
Affected and fixed versions
===========================
Fixed in 6.1.188 with commit 2239e6b49d33bb38817d69b4f0bf7d5cbde2ec68
Fixed in 6.6.157 with commit 4a0236fe97732e31cb4a6dcb433642f9e3ef9a56
Fixed in 6.12.110 with commit e351cb2d373f6f1d4f1eb7c9f30dc058c69c89f8
Fixed in 6.18.51 with commit 18b3433f10ee9c69e3252046028aa2be421f2d4d
Fixed in 7.2.5 with commit 84829e324a396668ceafb14723293b2863a74dcf
Fixed in 7.3-rc2 with commit 3785d40831ba5601296283e0197e10e089392757
Please see https://www.kernel.org for a full list of currently supported
kernel versions by the kernel community.
Unaffected versions might change over time as fixes are backported to
older supported kernel versions. The official CVE entry at
https://cve.org/CVERecord/?id=CVE-2026-89822
will be updated if fixes are backported, please check that for the most
up to date information about this issue.
Affected files
==============
The file(s) affected by this issue are:
drivers/gpu/drm/i915/i915_pci.c
Mitigation
==========
The Linux kernel CVE team recommends that you update to the latest
stable kernel version for this, and many other bugfixes. Individual
changes are never tested alone, but rather are part of a larger kernel
release. Cherry-picking individual commits is not recommended or
supported by the Linux kernel community at all. If however, updating to
the latest release is impossible, the individual changes to resolve this
issue can be found at these commits:
https://git.kernel.org/stable/c/2239e6b49d33bb38817d69b4f0bf7d5cbde2ec68
https://git.kernel.org/stable/c/4a0236fe97732e31cb4a6dcb433642f9e3ef9a56
https://git.kernel.org/stable/c/e351cb2d373f6f1d4f1eb7c9f30dc058c69c89f8
https://git.kernel.org/stable/c/18b3433f10ee9c69e3252046028aa2be421f2d4d
https://git.kernel.org/stable/c/84829e324a396668ceafb14723293b2863a74dcf
https://git.kernel.org/stable/c/3785d40831ba5601296283e0197e10e089392757
reply other threads:[~2026-09-16 10:34 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2026091601-CVE-2026-89822-e708@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=cve@kernel.org \
--cc=gregkh@kernel.org \
--cc=linux-cve-announce@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.