[CVE-2026-53058][LOW] drm/bridge: cadence: cdns-mhdp8546-core: Set the mhdp connector earlier in atomic_enable() [ Upstream

[AL-KERNEL <alkernel@kernelcve.org>]

CVE: CVE-2026-53058
Priority: LOW
AL-KERNEL base severity: LOW
KPANIC flag: NO
Patch: drm/bridge: cadence: cdns-mhdp8546-core: Set the mhdp connector earlier in atomic_enable() [ Upstream
Commit: 5302015daf26ef6b48e067f2b86c9482ac19e015
Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=5302015daf26ef6b48e067f2b86c9482ac19e015
Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-53058
Analysis date: Thu, 25 Jun 2026 04:52:03 -0400
ActionableScore: 1
ActionableScore lower bound: unknown
Actionable bucket: Ordinary Moderate / Low-like
Manual review required: NO

Summary:
A NULL pointer dereference in the Cadence MHDP DRM bridge recovery path can crash the kernel when atomic_enable fails before the connector pointer is initialized, requiring local DRM modeset access and affected hardware.

======================================================================
ABOUT THIS REPORT
======================================================================

The original Linux kernel CVE announcement for CVE-2026-53058 is available here:
https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-53058

The original announcement does not normally provide a security severity
estimate, CVSS assessment, or enough information to determine whether the
reported kernel bug represents a practically relevant security issue.

This report was generated by AL-KERNEL, an AI-assisted Linux kernel
vulnerability analysis system developed by Alexander Larkin. It combines
an autonomous classifier with LLM-assisted technical analysis and a
separate ActionableScore mechanism.

The purpose of this report is to prioritize Linux kernel CVEs before
manual review, identify cases that require prompt investigation, and
support automatic closure of issues that are unlikely to have meaningful
security impact.

Published priority for this report: LOW
Manual review required: NO

A detailed explanation of the methodology and priority rules is included
at the end of this message.

======================================================================
AL-KERNEL CLASSIFICATION RESULT
======================================================================

CVE-2026-53058	LOW	CHECK	Maybe valid. Check manually. Hints by AL-KERNEL: The best (paranoid) CVSS is 'AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H';**CWE-476;CWE-703;CWE-754;BEST CVSS score: '4.7';DESCR 'A NULL pointer dereference can occur in the Cadence MHDP DRM bridge when atomic_enable enters an error recovery path before the active connector has been recorded. In configurations using DRM_BRIDGE_ATTACH_NO_CONNECTOR, the connector is not initialized through the legacy bridge_attach path, so cdns_mhdp_modeset_retry_fn may later dereference a missing connector while trying to access mode_config locking data. For the CVSS the PR:L is used because practical triggering requires local access to DRM modeset control such as a DRM master or a local graphical session, not remote network input. AC:H is used because the crash depends on specific hardware, bridge configuration, and an error in link up or register access during enable. The issue is not network reachable. Impact is denial of service via kernel crash only. NO MANUAL CHECK REQUIRED COULD BE AUTOCLOSED.';NO MANUAL CHECK; ,and ActionableScore result is Ordinary Moderate / Low-like (with actual score 1) 	MAYBE	DANGER NULLPTR HARDWARE LINUS  DECREASED_TO_MODERATE_REGULAR_FROM_MODERATE7_BASED_ON_GUESSCVSS_AND_CIANNH DECREASED_TO_LOW_FROM_MODERATE_BASED_ON_ACTIONABLESCORELESSTHAN3	-	-	checked

======================================================================
ACTIONABLESCORE ANALYSIS
======================================================================

ActionableScore=1

## 1. ActionableScore

* Conservative score: **1**
* Paranoid score: **1**
* Final recommended bucket: **Ordinary Moderate / Low-like**::

## 2. Signal breakdown

Triggered signals:

* **Local unprivileged trigger: +1**
  Practical triggering may be possible from a local graphical session or DRM master capable of causing modeset operations.

* **Reliable kernel crash / strong DoS: +1**
  The described failure is a NULL pointer dereference in the DRM bridge recovery path, causing a kernel crash or oops.

Negative signals:

* **Hard or unreliable race / special timing or state required: -1**
  The bug requires a specific DRM bridge configuration, an atomic enable path, and an error in `cdns_mhdp_link_up()` or `cdns_mhdp_reg_read()` before the connector pointer is initialized.

* **Physical-only or rare hardware-only condition: -2**
  The affected code is specific to Cadence MHDP DRM bridge hardware and the `DRM_BRIDGE_ATTACH_NO_CONNECTOR` model.

Net: `+1 +1 -1 -2 = -1`, rounded/practically bucketed to **1** because there is still a real local DoS condition.

## 3. Reachability analysis

The issue is locally reachable through DRM/KMS modeset paths on systems using the affected Cadence MHDP bridge. It is not network reachable. Namespaces or containers usually do not make this broadly reachable unless the container is given direct DRM device access and sufficient modeset control. The path is hardware and configuration dependent, so exposure is narrow compared with core DRM or common GPU driver paths.

## 4. Severity interpretation

This behaves like an **ordinary Moderate / Low-like local DoS**, not an Important-class kernel vulnerability. The patch shows a NULL pointer dereference caused by using the connector before it is recorded in the device structure. There is no evidence of UAF, OOB write, arbitrary write, object lifetime takeover, information disclosure, or privilege escalation. The realistic impact is a local kernel crash on affected hardware under specific error conditions.

## 5. One-sentence report phrase

A NULL pointer dereference in the Cadence MHDP DRM bridge recovery path can crash the kernel when atomic_enable fails before the connector pointer is initialized, requiring local DRM modeset access and affected hardware.

## 6. Manual review recommendation

**NO MANUAL CHECK NEEDED**

This is a configuration and hardware dependent NULL dereference with DoS-only impact and no visible memory corruption primitive beyond invalid pointer dereference.

======================================================================
UPSTREAM PATCH SUMMARY
======================================================================

Patch: drm/bridge: cadence: cdns-mhdp8546-core: Set the mhdp connector earlier in atomic_enable() [ Upstream
Commit: 5302015daf26ef6b48e067f2b86c9482ac19e015
Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=5302015daf26ef6b48e067f2b86c9482ac19e015

Changed files:
  drivers/gpu/drm/bridge/cadence/cdns-mhdp8546-core.c
  drivers/gpu/drm/bridge/cadence/cdns-mhdp8546-core.h
  drivers/gpu/drm/bridge/cadence/cdns-mhdp8546-hdcp.c

Diff excerpt:

Not included in this email. See the upstream URL for the full patch.

Full patch:
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=5302015daf26ef6b48e067f2b86c9482ac19e015

======================================================================
DETAILED REPORT METHODOLOGY
======================================================================

The original Linux kernel CVE announcement for CVE-2026-53058 can be found here:
https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-53058

The original CVE announcement normally does not include a security-level
estimate. In particular, it may not contain a CVSS assessment, an impact
level, or enough information to determine whether the reported bug is a
practically relevant security issue. One purpose of this parallel CVE list
is to provide that missing technical and prioritization information.

The original goal of the AL-KERNEL project was to prioritize Linux kernel
CVE analysis automatically before manual review. The system can also help
identify non-security issues that may be suitable for automatic closure.

This report was generated by AL-KERNEL, an AI-assisted Linux kernel
vulnerability analysis system developed by Alexander Larkin.

The first analysis stage combines an autonomous classifier with additional
LLM-based analysis. The autonomous classifier runs locally on a CPU and is
based on a backpropagation neural network. Together, these mechanisms
produce a technical vulnerability description, identify likely weakness
types, estimate CVSS severity, and provide input for ActionableScore.

Two CVSS estimates are retained because incomplete kernel vulnerability
information often permits more than one defensible interpretation:

  Conservative CVSS vector: Not available
  The Best / paranoid CVSS vector: AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H
  The Best / paranoid CVSS score: 4.7

The conservative vector represents a lower-impact interpretation.
The Best/paranoid vector intentionally represents a plausible upper-bound
interpretation and should not automatically be treated as demonstrated
real-world impact.

CVSS may also need to be adjusted for a particular Linux deployment,
because actual reachability, privileges, enabled kernel configuration,
hardware, namespaces, exposed device nodes, and other environmental
conditions can differ significantly between systems.

A separate ActionableScore mechanism evaluates practical remediation
urgency. Its analysis may include reachability, attack prerequisites,
subsystem exposure, memory-corruption characteristics, denial-of-service
reliability, and possible confidentiality, integrity, or
privilege-escalation impact.

  Conservative ActionableScore: unknown
  Paranoid ActionableScore: 1

The final base severity is taken directly from the second tab-separated
field of the AL-KERNEL classification result. ActionableScore does not
replace or independently override that final AL-KERNEL decision, and
if ActionableScore adjusted impact level of ALKERNEL, then you would see
self-readable flags above like INCREASED_TO_HIGH_BASED_ON_ACTIONABLESCOREHIGHEREQTHAN7.

For an AL-KERNEL result of MODERATE, this report uses the following
additional presentation split:

  ActionableScore below 5   -> MODERATE REGULAR
  ActionableScore 5 or more -> MODERATE 7.0

The distinction between MODERATE REGULAR and MODERATE 7.0 makes it
possible to identify Moderate issues that should receive manual analysis
and fixes before lower-priority MODERATE REGULAR issues. In many cases,
MODERATE REGULAR fixes may wait for a later rebase or routine update.

There is one override in which MODERATE REGULAR becomes MODERATE 7.0
even when the ActionableScore is below 5. When the AL-KERNEL result
contains the KPANIC flag, a MODERATE result is always presented as
MODERATE 7.0. The KPANIC flag selected with few regexps without
usage of AI at all, so it helps to detect cases when Kernel Crash happens
and similar (to filter False-Negative results from the LLM usage).

KPANIC indicates that a reliable kernel crash, kernel panic, or similarly
serious kernel availability impact was identified by the classification
workflow.

AL-KERNEL base severity for this report: LOW
KPANIC detected for this report: NO
Published priority for this report (same as in Subject): LOW

These results are intended to support engineering triage. They are
machine-generated estimates, and cases marked for manual review should
be validated by a human security engineer before final disposition.
For more info read docs linked from here: https://kernelcve.org/
(and you can submit you own patch there to generate such a report
for non-existant CVE-id yet).

Note that in many cases this AI tool selects higher severity, than
real is (means you can expect Importants instead of Moderate 7.0 or
Moderates 7.0 instead of regular Moderates). If you see such cases,
please use reply email interface to add additional manual analyses
info to this particular CVE.
And please, please, let me know when you see Lows instead of Importants
or Important instead of Low (because particular for such cases I
need to tune this AI tool to make it better for this one and next similar).
My contact email for such notifications is alexanjelausa@gmail.com (and both
send reply to CVE record itself too and see "reply" button below for howto reply).