CVE-2026-53058
UnknownSummary
A vulnerability in the Linux kernel related to the incorrect setting of the mhdp pointer in the atomic_enable() function has been resolved. If errors occur in cdns_mhdp_link_up() or cdns_mhdp_reg_read(), it may lead to a NULL pointer dereference, causing a crash.
Risk Assessment
Organizations may be exposed to system crashes due to connection handling errors, potentially leading to service interruptions.
Recommendation
It is recommended to update the Linux kernel to the latest version to eliminate this vulnerability and avoid potential NULL pointer dereference issues.
Original NVD description (English source)
In the Linux kernel, the following vulnerability has been resolved: drm/bridge: cadence: cdns-mhdp8546-core: Set the mhdp connector earlier in atomic_enable() In case if we get errors in cdns_mhdp_link_up() or cdns_mhdp_reg_read() in atomic_enable, we will go to cdns_mhdp_modeset_retry_fn() and will hit NULL pointer while trying to access the mutex. We need the connector to be set before that. Unlike in legacy cases with flag !DRM_BRIDGE_ATTACH_NO_CONNECTOR, we do not have connector initialised in bridge_attach(), so add the mhdp->connector_ptr in device structure to handle both cases with DRM_BRIDGE_ATTACH_NO_CONNECTOR and !DRM_BRIDGE_ATTACH_NO_CONNECTOR, set it in atomic_enable() earlier to avoid possible NULL pointer dereference in recovery paths like modeset_retry_fn() with the DRM_BRIDGE_ATTACH_NO_CONNECTOR flag set.