CVE-2026-80658: drm/rockchip: dw_dp: Fix null-ptr-deref in dw_dp_remove()
In the Linux kernel, the following vulnerability has been resolved:
drm/rockchip: dwdp: Fix null-ptr-deref in dwdpremove()
Attempting to access driver data in the platform driver ->remove() callback may lead to a null pointer dereference since there is no guaranty that the component ->bind() callback invoking platformsetdrvdata() was executed.
A common scenario is when Rockchip DRM driver didn't manage to run componentbindall() because of an (unrelated) error causing early return from rockchipdrmbind().
Drop the unnecessary call to platformgetdrvdata() and, instead, reference the target device structure via platformdevice.
Event History
Frequently Asked Questions
Under what conditions can this be triggered?
The issue can occur when the Rockchip DRM driver's bind path returns early because component_bind_all() did not run successfully, such as after an unrelated error. The platform driver's remove callback can then attempt to access driver data that was never set.
What is the impact of a successful trigger?
Triggering the condition may cause a null pointer dereference in dw_dp_remove(), which can crash the affected kernel path during device removal or driver teardown.
Is this limited to a particular configuration state?
It depends on a failed Rockchip DRM component binding sequence rather than normal successful binding. Systems where the relevant component bind callback completes and sets the driver data do not encounter the missing-driver-data condition described.