CVE-2026-53058: drm/bridge: cadence: cdns-mhdp8546-core: Set the mhdp connector earlier in atomic_enable()
drm/bridge: cadence: cdns-mhdp8546-core: Set the mhdp connector earlier in atomicenable()
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 6.6.143.1-1 - Configuration
In atomic_enable(), initialize/set the mhdp connector pointer in the device structure before the code can reach cdns_mhdp_modeset_retry_fn() so that bridge_attach() does not encounter a NULL connector in recovery paths (e.g., when errors occur in cdns_mhdp_link_up() or cdns_mhdp_reg_read()).
Linux kernel DRM bridge (cadence cdns-mhdp8546-core) mhdp->connector_ptr initialization timing (DRM_BRIDGE_ATTACH_NO_CONNECTOR handling) = Set mhdp connector earlier in atomic_enable() before cdns_mhdp_modeset_retry_fn() can call bridge_attach() with DRM_BRIDGE_ATTACH_NO_CONNECTOR
Event History
Frequently Asked Questions
What is the severity of CVE-2026-53058?
The severity of CVE-2026-53058 is rated as risk 37.
How do I fix CVE-2026-53058?
To fix CVE-2026-53058, you need to update your Linux kernel to the latest version where this vulnerability has been addressed.
What type of vulnerability is CVE-2026-53058?
CVE-2026-53058 is classified as a Null Pointer Dereference vulnerability.
What component of the Linux kernel does CVE-2026-53058 affect?
CVE-2026-53058 affects the DRM (Direct Rendering Manager) bridge component related to the cadence CDNS-MHDP8546 core.
When was CVE-2026-53058 published?
CVE-2026-53058 was published on June 24, 2026.