CVE-2026-68429
drm/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.
INFO
Published Date :
Aug. 12, 2026, 12:17 a.m.
Last Modified :
Aug. 12, 2026, 12:17 a.m.
Remotely Exploit :
No
Source :
416baaa9-dc9f-4396-8d5f-8c081fb06d67
Affected Products
The following products are affected by CVE-2026-68429
vulnerability.
Even if cvefeed.io is aware of the exact versions of the
products
that
are
affected, the information is not represented in the table below.
No affected product recoded yet
Solution
- Apply the patch to the Linux kernel.
- Update the kernel to the fixed version.
- Test DP MST monitor connections and disconnections.
References to Advisories, Solutions, and Tools
Here, you will find a curated list of external links that provide in-depth
information, practical solutions, and valuable tools related to
CVE-2026-68429.
CWE - Common Weakness Enumeration
While CVE identifies
specific instances of vulnerabilities, CWE categorizes the common flaws or
weaknesses that can lead to vulnerabilities. CVE-2026-68429 is
associated with the following CWEs:
Common Attack Pattern Enumeration and Classification (CAPEC)
Common Attack Pattern Enumeration and Classification
(CAPEC)
stores attack patterns, which are descriptions of the common attributes and
approaches employed by adversaries to exploit the CVE-2026-68429
weaknesses.
We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).
Results are limited to the first 15 repositories due to potential performance issues.
The following list is the news that have been mention
CVE-2026-68429 vulnerability anywhere in the article.
The following table lists the changes that have been made to the
CVE-2026-68429 vulnerability over time.
Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.
-
New CVE Received by 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Aug. 12, 2026
Action Type Old Value New Value Added Affected [{'repo': 'https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git', 'vendor': 'Linux', 'product': 'Linux', 'versions': [{'status': 'affected', 'version': '5f57a96e92c60f62da91d58ceb5e5acd40e7d594', 'lessThan': 'b1d05cc61dfa6c4bd5e67855bec6a03e955f512d', 'versionType': 'git'}, {'status': 'affected', 'version': 'dbaeef363ea54f4c18112874b77503c72ba60fec', 'lessThan': '4ed6d08c4a59ee6a8cb806347f6d9873de5d229e', 'versionType': 'git'}, {'status': 'affected', 'version': 'dbaeef363ea54f4c18112874b77503c72ba60fec', 'lessThan': '8c6d84a54823cd839e6ce22af559925f1320c310', 'versionType': 'git'}, {'status': 'affected', 'version': 'dbaeef363ea54f4c18112874b77503c72ba60fec', 'lessThan': 'afdff9103818656627920c21822e48a6dae2906f', 'versionType': 'git'}, {'status': 'affected', 'version': 'dbaeef363ea54f4c18112874b77503c72ba60fec', 'lessThan': '613059875958e7b217b250ed14c3b189f9488421', 'versionType': 'git'}, {'status': 'affected', 'version': '6.6.86', 'lessThan': '6.6.148', 'versionType': 'semver'}], 'programFiles': ['drivers/gpu/drm/display/drm_dp_mst_topology.c'], 'defaultStatus': 'unaffected'}, {'repo': 'https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git', 'vendor': 'Linux', 'product': 'Linux', 'versions': [{'status': 'affected', 'version': '6.12'}, {'status': 'unaffected', 'version': '0', 'lessThan': '6.12', 'versionType': 'semver'}, {'status': 'unaffected', 'version': '6.6.148', 'versionType': 'semver', 'lessThanOrEqual': '6.6.*'}, {'status': 'unaffected', 'version': '6.12.101', 'versionType': 'semver', 'lessThanOrEqual': '6.12.*'}, {'status': 'unaffected', 'version': '6.18.42', 'versionType': 'semver', 'lessThanOrEqual': '6.18.*'}, {'status': 'unaffected', 'version': '7.1.6', 'versionType': 'semver', 'lessThanOrEqual': '7.1.*'}, {'status': 'unaffected', 'version': '7.2-rc2', 'versionType': 'original_commit_for_fix', 'lessThanOrEqual': '*'}], 'programFiles': ['drivers/gpu/drm/display/drm_dp_mst_topology.c'], 'defaultStatus': 'affected'}] Added 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. Added Reference https://git.kernel.org/stable/c/4ed6d08c4a59ee6a8cb806347f6d9873de5d229e Added Reference https://git.kernel.org/stable/c/613059875958e7b217b250ed14c3b189f9488421 Added Reference https://git.kernel.org/stable/c/8c6d84a54823cd839e6ce22af559925f1320c310 Added Reference https://git.kernel.org/stable/c/afdff9103818656627920c21822e48a6dae2906f Added Reference https://git.kernel.org/stable/c/b1d05cc61dfa6c4bd5e67855bec6a03e955f512d