drm/i915/bios: Tolerate devdata==NULL in intel_bios_encoder_supports_dp_dual_mode()
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 |
|
|
In the Linux kernel, the following vulnerability has been resolved:
drm/i915/bios: Tolerate devdata==NULL in intel_bios_encoder_supports_dp_dual_mode()
If we have no VBT, or the VBT didn't declare the encoder in question, we won't have the 'devdata' for the encoder. Instead of oopsing just bail early.
We won't be able to tell whether the port is DP++ or not, but so be it.
(cherry picked from commit 26410896206342c8a80d2b027923e9ee7d33b733)
From the CVE record · Linux
The drm/i915 BIOS code can trigger a kernel oops when an encoder has no device data because the VBT is absent or does not declare that encoder. The input does not describe an attacker action, access requirement, or user interaction.
Anyone running a Linux kernel with drm/i915 should check their kernel version; affected versions are not specified.