<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://db.gcve.eu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-11-03T08:14:31.810737+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@gcve.eu</email>
  </author>
  <link href="https://db.gcve.eu" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://db.gcve.eu/vuln/cve-2026-98786</id>
    <title>CVE-2026-98786 — drm/amd/display: guard dc_sink dereferences in MST mode validation</title>
    <updated>2026-11-03T08:14:31.811545+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Linux</p>
<p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>drm/amd/display: guard dc_sink dereferences in MST mode validation</p>
<p>dm_dp_mst_is_port_support_mode() reads
aconnector-&gt;dc_sink-&gt;dsc_caps... for the DSC branch-throughput check,
and get_conv_frl_bw()'s HDMI-PCON FRL-bandwidth path reads
aconnector-&gt;dc_sink-&gt;edid_caps.max_frl_rate, both without a NULL
check. dc_sink is cleared asynchronously on MST unplug, and both
functions run from paths that the driver's own comments document as
racing that teardown: the connector probe worker's -&gt;mode_valid
callback and a compositor's atomic check, neither of which holds the
MST manager lock that the teardown path uses. The former does have an
existing dsc_aux NULL check, but dsc_aux isn't reliably cleared in
every path that clears dc_sink, so it doesn't cover this.</p>
<p>Fail the port-support check and skip the FRL conversion path when the
sink is already gone.</p>
<p>(cherry picked from commit 7c3db8da4e039698ae198c870712428644e965c7)</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/cve-2026-98786"/>
  </entry>
</feed>
