dbcve.org
Linux KernelOperating system · Linux

CVE-2026-53058

MEDIUM · 5.5 CVSS v3.1 Published 2026-06-24
Fix available
A fix is available. Upgrade to 6.6.141 / 6.12.91 or later.
See remediation →
57/100
Remediation priority · Elevated
Zero-click 8 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

In the Linux kernel's Cadence MHDP8546 DRM bridge driver, a NULL pointer dereference occurs when error handling in atomic_enable() jumps to cdns_mhdp_modeset_retry_fn() before the mhdp connector is initialized. If cdns_mhdp_link_up() or cdns_mhdp_reg_read() fail, the recovery path attempts to access a mutex through an uninitialized connector pointer.

MitigationThe fix involves moving the mhdp->connector_ptr assignment earlier in atomic_enable() to ensure it's set before any error recovery paths can be triggered, preventing the NULL pointer dereference in both DRM_BRIDGE_ATTACH_NO_CONNECTOR and legacy configurations.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Linux KernelOperating system
Affected:>= 6.6, < 6.6.141>= 6.7, < 6.12.91>= 6.13, < 6.18.33>= 6.19, < 7.0.10

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check kernel version
    Run 'uname -r' to get the running kernel version
    Affected if The kernel version falls within >= 6.6, < 6.6.141; >= 6.7, < 6.12.91; >= 6.13, < 6.18.33; or >= 6.19, < 7.0.10
  2. Verify cdns-mhdp8546 driver presence
    Run 'modinfo cdns-mhdp8546' or check 'ls /sys/module | grep cdns-mhdp8546' to see if the driver module exists in the kernel
    Affected if The driver module is present in the kernel
  3. Detect Cadence MHDP hardware
    Run 'ls /sys/bus/platform/devices/ | grep -i mhdp' or check 'dmesg | grep -i mhdp' for driver loading messages
    Affected if A Cadence MHDP8546 device is present and the driver has attached to it
  4. Check DRM subsystem for bridge device
    Run 'ls /sys/class/drm/' and look for card entries, then check 'cat /sys/class/drm/card*/device/driver' for the cdns-mhdp8546 driver binding
    Affected if A DRM bridge device managed by cdns-mhdp8546 is registered in the system

A system is affected if it runs a kernel version in the affected ranges AND has Cadence MHDP8546 hardware with the cdns-mhdp8546 driver loaded and attached to a DRM bridge device.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 6.6.141 / 6.12.91 / 6.18.33 or later
Fixed in 6.6.1416.12.916.18.33
Interim mitigation

The fix involves moving the mhdp->connector_ptr assignment earlier in atomic_enable() to ensure it's set before any error recovery paths can be triggered, preventing the NULL pointer dereference in both DRM_BRIDGE_ATTACH_NO_CONNECTOR and legacy configurations.

Recommended fix High confidence

Upgrade to Linux kernel 6.6.141+, 6.12.91+, 6.18.33+, or 7.0.10+ depending on your current branch

  1. 1. Identify the currently running kernel version using `uname -r`
  2. 2. Determine which version branch your kernel is from (6.6.x, 6.7-6.12.x, 6.13-6.18.x, or 6.19-7.0.x)
  3. 3. Upgrade the Linux kernel to a version at or above the fixed version for your branch: for 6.6.x upgrade to >=6.6.141, for 6.7-6.12.x upgrade to >=6.12.91, for 6.13-6.18.x upgrade to >=6.18.33, or for 6.19-7.0.x upgrade to >=7.0.10
  4. 4. Update the kernel package using your distribution's package manager (e.g., `apt-get dist-upgrade`, `yum update`, or `dnf upgrade`)
  5. 5. Reboot the system to load the patched kernel
  6. 6. Verify the new kernel version is running with `uname -r`
Caveat Kernel upgrades may require matching system libraries and drivers; ensure compatibility with userspace tools before upgrading production systems

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Linux Kernel Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing6.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,020
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,232.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-53058 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-53058 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data