<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://vulnerability.circl.lu</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Fri, 02 Oct 2026 18:17:18 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-68429 — drm/dp_mst: Handle torn-down topology gracefully in drm_dp_mst_topology_queue_probe()</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-68429</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;drm/dp_mst: Handle torn-down topology gracefully in drm_dp_mst_topology_queue_probe()&lt;/p&gt;
&lt;p&gt;A hotplug or link-loss event can tear down the MST topology
(setting mgr-&amp;gt;mst_state = false and mgr-&amp;gt;mst_primary = NULL) concurrently
with a caller invoking drm_dp_mst_topology_queue_probe(). Since the check
is already performed under mgr-&amp;gt;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.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;The existing WARN_ON(mgr-&amp;gt;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.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;drm/dp_mst: Handle torn-down topology gracefully in drm_dp_mst_topology_queue_probe()&lt;/p&gt;
&lt;p&gt;A hotplug or link-loss event can tear down the MST topology
(setting mgr-&amp;gt;mst_state = false and mgr-&amp;gt;mst_primary = NULL) concurrently
with a caller invoking drm_dp_mst_topology_queue_probe(). Since the check
is already performed under mgr-&amp;gt;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.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;The existing WARN_ON(mgr-&amp;gt;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.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-68429</guid>
    </item>
  </channel>
</rss>
