CVE-2026-68429

UNRATEDCVSS · not yet scoredTrending — 5 sources updated this week
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • No CVSS published and no exploitation signals yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS v2: Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
EchelonGraph score
Not yet assessedNo source has published severity data for this CVE yet — no CVSS score from NVD or a CNA, no GitHub advisory, and it is not in CISA KEV. This is not a rating of zero; we cannot assess it yet.
EG Score
EG Risk
EPSS PROB
0%
EPSS %ILE
7%
KEV
Not listed

Published

August 12, 2026

Last Modified

August 17, 2026

Vendor Advisories for CVE-2026-68429(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Data Freshness Timeline

(refreshed 13× in last 7d / 17× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-08-20 22:56 UTCEPSS rescore
  2. 2026-08-20 08:53 UTCGHSA enrichment
  3. 2026-08-19 17:04 UTCEPSS rescore
  4. 2026-08-17 13:47 UTCEPSS rescore
  5. 2026-08-17 06:31 UTCGHSA enrichment
  6. 2026-08-17 06:18 UTCNVD update
  7. 2026-08-17 05:35 UTCGHSA enrichment
  8. 2026-08-17 05:24 UTCMITRE cvelistV5
  9. 2026-08-16 14:56 UTCEPSS rescore
  10. 2026-08-16 14:56 UTCEPSS rescore
  11. 2026-08-15 02:44 UTCEG score recompute
  12. 2026-08-15 02:44 UTCGHSA enrichment
  13. 2026-08-15 01:30 UTCEPSS rescore
  14. 2026-08-12 13:51 UTCEPSS rescore
  15. 2026-08-12 00:19 UTCNVD update
  16. 2026-08-12 00:15 UTCEG score recompute
  17. 2026-08-12 00:15 UTCMITRE cvelistV5first tracked

Frequently asked(4)

What is CVE-2026-68429?
CVE-2026-68429 is a publicly disclosed vulnerability published on August 12, 2026. In the Linux kernel, the following vulnerability has been resolved: drm/dpmst: Handle torn-down topology gracefully in drmdpmsttopologyqueueprobe() A hotplug or link-loss event can tear down the MST topology (setting mgr->mststate = false and mgr->mstprimary = NULL) concurrently with a caller…
When was CVE-2026-68429 disclosed?
CVE-2026-68429 was first published in the National Vulnerability Database on August 12, 2026, with the most recent update on August 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-68429 actively exploited?
CVE-2026-68429 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 93.4% of all scored CVEs.
How do I remediate CVE-2026-68429?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-68429, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-68429

Explore →

Is Your Infrastructure Affected by CVE-2026-68429?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.