drm/i915: Grab intel_display from the encoder to avoid potential oopsies
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.12.1146.13.26.14In the Linux kernel, the following vulnerability has been resolved:
drm/i915: Grab intel_display from the encoder to avoid potential oopsies
Grab the intel_display from 'encoder' rather than 'state' in the encoder hooks to avoid the massive footgun that is intel_sanitize_encoder(), which passes NULL as the 'state' argument to encoder .disable() and .post_disable().
TODO: figure out how to actually fix intel_sanitize_encoder()...
From the CVE record · Linux
The Linux kernel’s drm/i915 encoder hooks can encounter a NULL state argument when intel_sanitize_encoder() calls disable() or post_disable(), potentially causing a kernel oops. The input does not establish whether an attacker can trigger this or specify access, authentication, or user-interaction requirements.
Engineers running the Linux kernel with drm/i915 should check their installations; affected versions are not specified.