CVE-2026-98782: drm/mediatek: Fix ovl adaptor platform device leak
drm/mediatek: Fix ovl adaptor platform device leak
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 6.6.160 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 6.12.113 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 6.18.56 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 7.2.10 - Upgrade
Upgrade
azurelinux/kernelto a version that resolves this vulnerability.Fixed in 6.6.161.1-1 - Compensating control
Update the MediaTek DRM driver so mtk_drm_probe() tracks successful OVL adaptor platform-device registration, recovers the device from the stored DDP component device, and unregisters it both on probe failure and during normal removal.
Event History
Frequently Asked Questions
Which systems are affected by this lifecycle issue?
It applies to MediaTek DRM display pipelines that require the OVL adaptor platform device. The stale device can be left behind when a later DRM probe initialization step fails or when the DRM driver is normally removed.
What condition causes the leaked device to remain registered?
The OVL adaptor must have been successfully registered before a subsequent initialization failure occurs. It is also left registered when the DRM driver is unbound because the prior remove path did not unregister it.
What should be done if the driver cannot be updated immediately?
Avoid unbinding or removing the affected DRM driver where practical, since the normal removal path is one trigger for leaving the adaptor device registered. Recovery requires unregistering the previously registered OVL adaptor platform device; the provided fixes add this cleanup for both probe failures and normal removal.