drm/i915: Guard against NULL driver_data in i915_pci_probe()
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 782a985d7af26db39e86070d28f987cad21313c0 · < 3785d40831ba5601296283e0197e10e089392757| No fix yet |
| Linux Linux |
|
|
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)
From the CVE record · Linux
The Linux kernel's i915 PCI probe can dereference a NULL pointer when a device is force-bound through sysfs driver_override. A local attacker able to force-bind a device this way could trigger the dereference; the input does not specify authentication requirements or whether user interaction is needed.
Engineers running Linux kernels with the drm/i915 driver should check their affected versions; no version range is provided.