drm/mediatek: Add vblank register/unregister callback functions
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/mediatek: Add vblank register/unregister callback functions
We encountered a kernel panic issue that callback data will be NULL when it's using in ovl irq handler. There is a timing issue between mtk_disp_ovl_irq_handler() and mtk_ovl_disable_vblank().
To resolve this issue, we use the flow to register/unregister vblank cb: - Register callback function and callback data when crtc creates. - Unregister callback function and callback data when crtc destroies.
With this solution, we can assure callback data will not be NULL when vblank is disable.
From the CVE record · Linux
A timing issue between the MediaTek overlay interrupt handler and vblank disable path can leave callback data NULL and cause a kernel panic. The input does not specify how an attacker could trigger it or whether access, authentication, or user interaction is required.
Engineers running Linux kernels with the MediaTek DRM driver should check whether their kernel includes the fix; affected versions are not specified.