drm/i915: Make intel_get_crtc_new_encoder() less oopsy
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 3a47ae201e074945bbde0b088e4c1215c07f4d75 · < 631420b06597a33c72b6dcef78d1c2dea17f452d| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
drm/i915: Make intel_get_crtc_new_encoder() less oopsy
The point of the WARN was to print something, not oops straight up. Currently that is precisely what happens if we can't find the connector for the crtc in the atomic state. Get the dev pointer from the atomic state instead of the potentially NULL encoder to avoid that.
(cherry picked from commit 3b6692357f70498f617ea1b31a0378070a0acf1c)
From the CVE record · Linux
The Linux kernel’s drm/i915 code can trigger an oops when it cannot find a connector for a CRTC in the atomic state and then accesses a potentially NULL encoder. The input does not establish whether an attacker can trigger this condition or specify network access, authentication, or user-interaction requirements.
Engineers running Linux kernels with drm/i915 should check their kernel versions against the vendor advisory; affected versions are not specified in the input.