drm/exynos: exynos7_drm_decon: add vblank check in IRQ handling
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 96976c3d9aff4e1387c30f6356ac01fa6f72ef46 · < e9d9b25f376737b81f06de9c5aa422b488f47184| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
drm/exynos: exynos7_drm_decon: add vblank check in IRQ handling
If there's support for another console device (such as a TTY serial), the kernel occasionally panics during boot. The panic message and a relevant snippet of the call stack is as follows:
Unable to handle kernel NULL pointer dereference at virtual address 000000000000000 Call trace: drm_crtc_handle_vblank+0x10/0x30 (P) decon_irq_handler+0x88/0xb4 [...]
Otherwise, the panics don't happen. This indicates that it's some sort of race condition.
Add a check to validate if the drm device can handle vblanks before calling drm_crtc_handle_vblank() to avoid this.
From the CVE record · Linux
The Linux kernel's Exynos7 DRM interrupt handler can dereference a null pointer during boot when another console device, such as a serial TTY, is supported. This can cause an occasional kernel panic; the input does not describe an attacker, authentication requirement, or user interaction.
Engineers running Linux kernels with Exynos7 DRM support should check their builds; affected versions are not specified.