CVE-2026-89822: drm/i915: Guard against NULL driver_data in i915_pci_probe()
drm/i915: Guard against NULL driverdata in i915pciprobe()
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 6.6.157.1-1 - Upgrade
Upgrade
debian/linuxto a version that resolves this vulnerability.Fixed in 6.1.190-1Fixed in 6.12.115-2Fixed in 7.2.12-1Fixed in 7.2.15-1 - Upgrade
Upgrade
debian/linux-6.12to a version that resolves this vulnerability.Fixed in 6.12.113-1~deb12u1 - Upgrade
Upgrade
ubuntu/linux-hwe-7.0to a version that resolves this vulnerability.Fixed in 7.0.0-42.42~24.04.1 - Upgrade
Upgrade
ubuntu/linux-riscv-7.0to a version that resolves this vulnerability.Fixed in 7.0.0-42.42.1~24.04.1 - Upgrade
Upgrade
ubuntu/linuxto a version that resolves this vulnerability.Fixed in 7.0.0-42.42 - Upgrade
Upgrade
ubuntu/linux-awsto a version that resolves this vulnerability.Fixed in 7.0.0-1016.17 - Upgrade
Upgrade
ubuntu/linux-gcpto a version that resolves this vulnerability.Fixed in 7.0.0-1016.18 - Upgrade
Upgrade
ubuntu/linux-ibmto a version that resolves this vulnerability.Fixed in 7.0.0-1017.17 - Upgrade
Upgrade
ubuntu/linux-oem-7.0to a version that resolves this vulnerability.Fixed in 7.0.0-1017.17 - Upgrade
Upgrade
ubuntu/linux-oracleto a version that resolves this vulnerability.Fixed in 7.0.0-1015.16 - Upgrade
Upgrade
ubuntu/linux-riscvto a version that resolves this vulnerability.Fixed in 7.0.0-42.42.1 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Patch 2727922084672cc274ecea726ea00363c2893731
Event History
Frequently Asked Questions
Who is exposed to this issue?
Systems using the Linux kernel i915 DRM driver are exposed when a PCI device is force-bound to i915 through the sysfs driver_override mechanism.
What must an attacker or local user do to trigger the failure?
They must force-bind a device through sysfs driver_override so that pci_match_device() returns the dummy pci_device_id_any entry, which has no driver_data. The i915 probe path then dereferences the resulting NULL device-information pointer.
Is this triggered during normal i915 device matching?
The described NULL pointer condition occurs specifically when force-binding via sysfs driver_override causes the dummy PCI match entry to be returned. The provided information does not indicate that normal matching produces this condition.
What is the impact of a successful trigger?
The affected probe path can dereference a NULL pointer, resulting in a kernel NULL-pointer dereference.