Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

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

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.

Timeline

  1. ID reserved

    By Linux

  2. · 13 days later

    Published

  3. · 3 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.

EPSS (exploitation in 30 days)
0.17% · top 94% of all CVEs (13 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.

Affected products

  • Linux · Linux

    • affected 5f57a96e92c60f62da91d58ceb5e5acd40e7d594 – < b1d05cc61dfa6c4bd5e67855bec6a03e955f512d
    • affected dbaeef363ea54f4c18112874b77503c72ba60fec – < 4ed6d08c4a59ee6a8cb806347f6d9873de5d229e
    • affected dbaeef363ea54f4c18112874b77503c72ba60fec – < 8c6d84a54823cd839e6ce22af559925f1320c310
    • affected dbaeef363ea54f4c18112874b77503c72ba60fec – < afdff9103818656627920c21822e48a6dae2906f
    • affected dbaeef363ea54f4c18112874b77503c72ba60fec – < 613059875958e7b217b250ed14c3b189f9488421
    • affected 6.6.86 – < 6.6.148
  • Linux · Linux

    • affected 6.12
    • unaffected < 6.12
    • unaffected 6.6.148 – ≤ 6.6.*
    • unaffected 6.12.101 – ≤ 6.12.*
    • unaffected 6.18.42 – ≤ 6.18.*
    • unaffected 7.1.6 – ≤ 7.1.*
    • unaffected 7.2 – ≤ *

References

References5

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-68429 badge
[![CVE-2026-68429](https://cveledger.app/badge/CVE-2026-68429.svg)](https://cveledger.app/cve/CVE-2026-68429)

Record last updated .