drm/i915: Fix NULL ptr deref by checking new_crtc_state
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
6.1.306.3.46.4In the Linux kernel, the following vulnerability has been resolved:
drm/i915: Fix NULL ptr deref by checking new_crtc_state
intel_atomic_get_new_crtc_state can return NULL, unless crtc state wasn't obtained previously with intel_atomic_get_crtc_state, so we must check it for NULLness here, just as in many other places, where we can't guarantee that intel_atomic_get_crtc_state was called. We are currently getting NULL ptr deref because of that, so this fix was confirmed to help.
(cherry picked from commit 1d5b09f8daf859247a1ea65b0d732a24d88980d8)
From the CVE record · Linux
The Linux kernel’s drm/i915 code can dereference a NULL pointer when intel_atomic_get_new_crtc_state returns NULL. The input does not specify an attacker action or whether triggering this requires network access, authentication, or user interaction.
Engineers running Linux kernels with drm/i915 should check their builds; affected versions are not specified.