Bug 2514439 (CVE-2026-68429) - CVE-2026-68429 kernel: drm/dp_mst: Handle torn-down topology gracefully in drm_dp_mst_topology_queue_probe()
Summary: CVE-2026-68429 kernel: drm/dp_mst: Handle torn-down topology gracefully in dr...
Keywords:
Status: NEW
Alias: CVE-2026-68429
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Product Security
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-08-12 00:21 UTC by OSIDB Bzimport
Modified: 2026-08-13 09:14 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

Description OSIDB Bzimport 2026-08-12 00:21:24 UTC
In the Linux kernel, the following vulnerability has been resolved:

drm/dp_mst: Handle torn-down topology gracefully in drm_dp_mst_topology_queue_probe()

A hotplug or link-loss event can tear down the MST topology
(setting mgr->mst_state = false and mgr->mst_primary = NULL) concurrently
with a caller invoking drm_dp_mst_topology_queue_probe(). Since the check
is already performed under mgr->lock, the condition is not a programming
error but a valid race -- the topology was valid when the caller decided
to call this function, but was torn down before the lock was acquired.

Replace the drm_WARN_ON() with a graceful early return. This eliminates
spurious kernel warnings and the resulting compositor crashes observed
when connecting/disconnecting DP MST monitors, while keeping the correct
behavior of doing nothing when MST is not active. A drm_dbg_mst() trace
is added so the skipped probe remains observable under MST debug logging.

The existing WARN_ON(mgr->mst_primary) in drm_dp_mst_topology_mgr_set_mst()
already catches the case where the topology is initialized twice, so no
diagnostic coverage is lost.

Comment 1 Mauro Matteo Cascella 2026-08-12 15:56:29 UTC
Upstream advisory:
https://lore.kernel.org/linux-cve-announce/2026081251-CVE-2026-68429-d0b9@gregkh/T


Note You need to log in before you can comment on or make changes to this bug.