drm/dp_mst: Handle torn-down topology gracefully in drm_dp_mst_topology_queue_probe()
Summary
| CVE | CVE-2026-68429 |
|---|---|
| State | PUBLISHED |
| Assigner | Linux |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2026-08-12 00:17:42 UTC |
| Updated | 2026-08-17 06:17:51 UTC |
| Description | 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. |
Risk And Classification
EPSS: 0.001680000 probability, percentile 0.065600000 (date 2026-08-17)
Vendor Declared Affected Products
| Source | Vendor | Product | Version | Platforms |
|---|---|---|---|---|
| CNA | Linux | Linux | affected 5f57a96e92c60f62da91d58ceb5e5acd40e7d594 b1d05cc61dfa6c4bd5e67855bec6a03e955f512d git | Not specified |
| CNA | Linux | Linux | affected dbaeef363ea54f4c18112874b77503c72ba60fec 4ed6d08c4a59ee6a8cb806347f6d9873de5d229e git | Not specified |
| CNA | Linux | Linux | affected dbaeef363ea54f4c18112874b77503c72ba60fec 8c6d84a54823cd839e6ce22af559925f1320c310 git | Not specified |
| CNA | Linux | Linux | affected dbaeef363ea54f4c18112874b77503c72ba60fec afdff9103818656627920c21822e48a6dae2906f git | Not specified |
| CNA | Linux | Linux | affected dbaeef363ea54f4c18112874b77503c72ba60fec 613059875958e7b217b250ed14c3b189f9488421 git | Not specified |
| CNA | Linux | Linux | affected 6.6.86 6.6.148 semver | Not specified |
| CNA | Linux | Linux | affected 6.12 | Not specified |
| CNA | Linux | Linux | unaffected 6.12 semver | Not specified |
| CNA | Linux | Linux | unaffected 6.6.148 6.6.* semver | Not specified |
| CNA | Linux | Linux | unaffected 6.12.101 6.12.* semver | Not specified |
| CNA | Linux | Linux | unaffected 6.18.42 6.18.* semver | Not specified |
| CNA | Linux | Linux | unaffected 7.1.6 7.1.* semver | Not specified |
| CNA | Linux | Linux | unaffected 7.2 * original_commit_for_fix | Not specified |
References
| Reference | Source | Link | Tags |
|---|---|---|---|
| git.kernel.org/stable/c/8c6d84a54823cd839e6ce22af559925f1320c310 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/afdff9103818656627920c21822e48a6dae2906f | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/613059875958e7b217b250ed14c3b189f9488421 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/4ed6d08c4a59ee6a8cb806347f6d9873de5d229e | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/b1d05cc61dfa6c4bd5e67855bec6a03e955f512d | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| CVE Program record | CVE.ORG | www.cve.org | canonical |
| NVD vulnerability detail | NVD | nvd.nist.gov | canonical, analysis |
No vendor comments have been submitted for this CVE.
There are currently no legacy QID mappings associated with this CVE.