drm/mediatek: Clean dangling pointer on bind error path
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 119f5173628aa7a0c3cf9db83460d40709e8241d · < f3887c771576c5d740c5c5b8bf654a8ab8020b7d| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
drm/mediatek: Clean dangling pointer on bind error path
mtk_drm_bind() can fail, in which case drm_dev_put() is called, destroying the drm_device object. However a pointer to it was still being held in the private object, and that pointer would be passed along to DRM in mtk_drm_sys_prepare() if a suspend were triggered at that point, resulting in a panic. Clean the pointer when destroying the object in the error path to prevent this from happening.
From the CVE record · Linux
In the Linux kernel’s MediaTek DRM driver, a failed bind can leave a dangling pointer to a destroyed DRM device. If a suspend occurs at that point, the pointer can be passed to DRM and cause a kernel panic. The input does not establish whether an attacker can trigger these conditions or what access would be required.
Engineers running Linux kernels with the MediaTek DRM driver should check their versions; affected versions are not specified.