Skip to main content

Linux Kernel CVE-2026-53058

| EUVDEUVD-2026-38926 MEDIUM
NULL Pointer Dereference (CWE-476)
2026-06-24 Linux GHSA-rc9r-g4hp-h8v7
5.5
CVSS 3.1 · NVD
Share

Severity by source

NVD PRIMARY
5.5 MEDIUM
AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
vuln.today AI
5.5 MEDIUM

AV:L and PR:L confirmed by local driver context; A:H for kernel panic; no confidentiality or integrity impact; AC:L as no race condition is required beyond triggering a link error.

3.1 AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
4.0 AV:L/AC:L/AT:P/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N
SUSE
MEDIUM
qualitative
Red Hat
5.5 LOW
qualitative

Primary rating from NVD.

CVSS VectorNVD

Attack Vector
Local
Attack Complexity
Low
Privileges Required
Low
User Interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

Lifecycle Timeline

5
Analysis Generated
Jul 21, 2026 - 17:38 vuln.today
CVSS changed
Jul 21, 2026 - 17:37 NVD
5.5 (MEDIUM)
Patch available
Jun 24, 2026 - 18:02 EUVD
CVE Published
Jun 24, 2026 - 16:30 cve.org
UNKNOWN (no severity yet)
CVE Published
Jun 24, 2026 - 16:30 nvd
MEDIUM 5.5

DescriptionNVD

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.

AnalysisAI

NULL pointer dereference in the Linux kernel's DRM Cadence MHDP8546 DisplayPort bridge driver (cdns-mhdp8546-core) can be triggered by a local low-privileged user on systems with the affected hardware, causing a kernel panic and complete system availability loss. The flaw arises when error recovery paths in cdns_mhdp_modeset_retry_fn() attempt to access a mutex via a connector pointer that has not yet been initialized in the DRM_BRIDGE_ATTACH_NO_CONNECTOR code path. No public exploit code or active exploitation (CISA KEV) has been identified; patches are available across multiple stable kernel branches.

Technical ContextAI

The affected component is the Linux kernel DRM/KMS subsystem's Cadence MHDP8546 DisplayPort bridge driver (drivers/gpu/drm/bridge/cadence/cdns-mhdp8546-core.c). The driver supports two attachment modes: legacy (!DRM_BRIDGE_ATTACH_NO_CONNECTOR), where the connector is initialized in bridge_attach(), and the newer DRM_BRIDGE_ATTACH_NO_CONNECTOR mode, where it is not. In the latter path, if cdns_mhdp_link_up() or cdns_mhdp_reg_read() fails during atomic_enable(), the recovery function cdns_mhdp_modeset_retry_fn() is invoked. This function dereferences mhdp->connector_ptr to access a mutex, but the pointer has not yet been assigned - it was supposed to be set later in atomic_enable(). CWE-476 (NULL Pointer Dereference) describes this class of flaw where a null pointer is dereferenced before it is validated or assigned. CPE: cpe:2.3:a:linux:linux:*:*:*:*:*:*:*:*. The bug was introduced by commit c932ced6b58524eeb948ff252f6512cd6bcb9d9f.

RemediationAI

The primary fix is to upgrade to a patched stable kernel release: 6.6.141, 6.12.91, 6.18.33, 7.0.10, or any 7.1+ build. Fix commits are available on kernel.org at https://git.kernel.org/stable/c/5302015daf26ef6b48e067f2b86c9482ac19e015 (6.6 branch), https://git.kernel.org/stable/c/a3611554e599d1a24b45fd8415bacb72ce861e4b, https://git.kernel.org/stable/c/cf2ac2cac8b319f89b3a3851ca0c5ffb6a549575, https://git.kernel.org/stable/c/1af3b42e08a957e53bab8e1897393fe0a27d9fbf, and https://git.kernel.org/stable/c/43d6508ddbf9fb974fbc359a033154f78c9d4c8b. Ubuntu users should apply USN-8566-1, USN-8567-1, or USN-8568-1 per their kernel track (https://ubuntu.com/security/notices/USN-8568-1). On systems where a kernel upgrade cannot be immediately applied and the Cadence MHDP8546 hardware is present, the compensating control is to blacklist the cdns-mhdp8546 kernel module (modprobe.d blacklist entry), which disables the driver and prevents the code path from being reached; this trades off display output on the affected bridge hardware for the duration of the deferral.

Vendor StatusVendor

SUSE

Severity: Moderate
Product Status
Image SLES15-SP7-Azure-3P Image SLES15-SP7-Azure-Basic Image SLES15-SP7-Azure-Standard Image SLES15-SP7-HPC-Azure Affected
Image SLES15-SP7-BYOS-Azure Image SLES15-SP7-BYOS-GCE Image SLES15-SP7-CHOST-BYOS-Aliyun Image SLES15-SP7-CHOST-BYOS-Azure Image SLES15-SP7-CHOST-BYOS-EC2 Image SLES15-SP7-CHOST-BYOS-GCE Image SLES15-SP7-CHOST-BYOS-GDC Image SLES15-SP7-CHOST-BYOS-SAP-CCloud Image SLES15-SP7-EC2 Image SLES15-SP7-EC2-ECS-HVM Image SLES15-SP7-GCE Image SLES15-SP7-HPC-BYOS-Azure Image SLES15-SP7-HPC-BYOS-EC2 Image SLES15-SP7-HPC-BYOS-GCE Image SLES15-SP7-Hardened-BYOS-Azure Image SLES15-SP7-Hardened-BYOS-EC2 Image SLES15-SP7-Hardened-BYOS-GCE Image SLES15-SP7-SAPCAL-Azure Image SLES15-SP7-SAPCAL-EC2 Image SLES15-SP7-SAPCAL-GCE Affected
Image SLES15-SP7-SAP-Azure Image SLES15-SP7-SAP-Azure-3P Image SLES15-SP7-SAP-BYOS-Azure Image SLES15-SP7-SAP-BYOS-EC2 Image SLES15-SP7-SAP-BYOS-GCE Image SLES15-SP7-SAP-EC2 Image SLES15-SP7-SAP-GCE Image SLES15-SP7-SAP-Hardened-Azure Image SLES15-SP7-SAP-Hardened-BYOS-Azure Image SLES15-SP7-SAP-Hardened-BYOS-EC2 Image SLES15-SP7-SAP-Hardened-BYOS-GCE Image SLES15-SP7-SAP-Hardened-GCE Affected
SUSE Linux Enterprise Desktop 15 SP7 Fixed
SUSE Linux Enterprise High Availability Extension 15 SP7 Fixed

Share

CVE-2026-53058 vulnerability details – vuln.today

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy