CVE-2026-68429: drm/dp_mst: Handle torn-down topology gracefully in drm_dp_mst_topology_queue_probe()
Noroxi assessment
Priority: Monitor (action score 0/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.16% (FIRST EPSS).
- Fixed version: Linux Linux 4ed6d08c4a59ee6a8cb806347f6d9873de5d229e, 6.6.148, 613059875958e7b217b250ed14c3b189f9488421; azl3 kernel 6.6.143.1-1 on Azure Linux 3.0 6.6.150.1-1.
Low priority for now. Upgrade to Linux Linux 4ed6d08c4a59ee6a8cb806347f6d9873de5d229e, 6.6.148, 613059875958e7b217b250ed14c3b189f9488421; azl3 kernel 6.6.143.1-1 on Azure Linux 3.0 6.6.150.1-1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Aug 11, 2026
- Updated
- Aug 17, 2026
- EPSS
- 0.1% · 6th percentile
- CWE
- —
Report tools
Action score
0
Monitor
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 6.12affected
- 5f57a96e92c60f62da91d58ceb5e5acd40e7d594 and later · before b1d05cc61dfa6c4bd5e67855bec6a03e955f512daffected · git
- dbaeef363ea54f4c18112874b77503c72ba60fec and later · before 4ed6d08c4a59ee6a8cb806347f6d9873de5d229eaffected · git
- dbaeef363ea54f4c18112874b77503c72ba60fec and later · before 8c6d84a54823cd839e6ce22af559925f1320c310affected · git
- dbaeef363ea54f4c18112874b77503c72ba60fec and later · before afdff9103818656627920c21822e48a6dae2906faffected · git
- dbaeef363ea54f4c18112874b77503c72ba60fec and later · before 613059875958e7b217b250ed14c3b189f9488421affected · git
- 6.6.86 and later · before 6.6.148affected · semver
- before 6.12not affected · semver
- 6.6.148 and later · up to and including 6.6.*not affected · semver
- 6.12.101 and later · up to and including 6.12.*not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux-6.12 | before 6.12.101-1~deb12u1 | 6.12.101-1~deb12u1 |
| Debian:13 | linux | before 6.12.101-1 | 6.12.101-1 |
| Debian:14 | linux | before 7.1.6-1 | 7.1.6-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-68426Aug 10, 2026 · xfrm: fix stale skb->prev after async crypto steals a GSO segment39Monitor
- ← EarlierCVE-2026-68427Aug 10, 2026 · gpu: host1x: Fix use-after-free in host1x_bo_clear_cached_mappings31Monitor
- Later →CVE-2026-68430Aug 11, 2026 · drm/amdgpu/gfx8: drop unecessary BUG_ON()0Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 4ed6d08c4a59ee6a8cb806347f6d9873de5d229e | Vendor (CNA) |
| Linux Linux | 6.6.148 | Vendor (CNA) |
| Linux Linux | 613059875958e7b217b250ed14c3b189f9488421 | Vendor (CNA) |
| Linux Linux | 8c6d84a54823cd839e6ce22af559925f1320c310 | Vendor (CNA) |
| Linux Linux | afdff9103818656627920c21822e48a6dae2906f | Vendor (CNA) |
| Linux Linux | b1d05cc61dfa6c4bd5e67855bec6a03e955f512d | Vendor (CNA) |
| azl3 kernel 6.6.143.1-1 on Azure Linux 3.0 | 6.6.150.1-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| debian:linux | 6.12.101-1 · Debian:13 | Package registry (OSV) |
| debian:linux-6.12 | 6.12.101-1~deb12u1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
No CVSS vector for this record, so attack conditions can't be derived.
Weakness class (CWE)
—
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (4 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.