Description
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)
Affected products
linux: linux kernel
References6
- git.kernel.org/stable/c/0fe6ef82e4f4764e8f556632e4cd93d78d448e99 Patch
- git.kernel.org/stable/c/54202488c835dab8c648acd107f0bb8eaa699894 Patch
- git.kernel.org/stable/c/631420b06597a33c72b6dcef78d1c2dea17f452d Patch
- git.kernel.org/stable/c/780f303233c35eeb5132e3ee1cbc8f4cebe86dd2 Patch
- git.kernel.org/stable/c/8cd725315c559a8a4d18ac1d7fce1d6b9a667529 Patch
- git.kernel.org/stable/c/fd8b0abecdf66379e9d25d7448b942b5be379cb2 Patch
Metrics
- CVSS 3.1
-
5.5
MEDIUM
Score source: NVD
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H - EPSS — exploit probability
- 0% percentile: 4 · as of 9 November 2026
Could this be exploited in your environment?
A patch closes the known hole. A penetration test shows what an attacker can still reach — with proof.