<?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://db.gcve.eu</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>Tue, 03 Nov 2026 08:13:18 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-98786</title>
      <link>https://db.gcve.eu/vuln/fkie_cve-2026-98786</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;drm/amd/display: guard dc_sink dereferences in MST mode validation&lt;/p&gt;
&lt;p&gt;dm_dp_mst_is_port_support_mode() reads
aconnector-&amp;gt;dc_sink-&amp;gt;dsc_caps... for the DSC branch-throughput check,
and get_conv_frl_bw()&amp;#39;s HDMI-PCON FRL-bandwidth path reads
aconnector-&amp;gt;dc_sink-&amp;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&amp;#39;s own comments document as
racing that teardown: the connector probe worker&amp;#39;s -&amp;gt;mode_valid
callback and a compositor&amp;#39;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&amp;#39;t reliably cleared in
every path that clears dc_sink, so it doesn&amp;#39;t cover this.&lt;/p&gt;
&lt;p&gt;Fail the port-support check and skip the FRL conversion path when the
sink is already gone.&lt;/p&gt;
&lt;p&gt;(cherry picked from commit 7c3db8da4e039698ae198c870712428644e965c7)&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;drm/amd/display: guard dc_sink dereferences in MST mode validation&lt;/p&gt;
&lt;p&gt;dm_dp_mst_is_port_support_mode() reads
aconnector-&amp;gt;dc_sink-&amp;gt;dsc_caps... for the DSC branch-throughput check,
and get_conv_frl_bw()&amp;#39;s HDMI-PCON FRL-bandwidth path reads
aconnector-&amp;gt;dc_sink-&amp;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&amp;#39;s own comments document as
racing that teardown: the connector probe worker&amp;#39;s -&amp;gt;mode_valid
callback and a compositor&amp;#39;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&amp;#39;t reliably cleared in
every path that clears dc_sink, so it doesn&amp;#39;t cover this.&lt;/p&gt;
&lt;p&gt;Fail the port-support check and skip the FRL conversion path when the
sink is already gone.&lt;/p&gt;
&lt;p&gt;(cherry picked from commit 7c3db8da4e039698ae198c870712428644e965c7)&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/fkie_cve-2026-98786</guid>
    </item>
    <item>
      <title>GHSA-7r8j-xcf8-cxq6</title>
      <link>https://db.gcve.eu/vuln/ghsa-7r8j-xcf8-cxq6</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;drm/amd/display: guard dc_sink dereferences in MST mode validation&lt;/p&gt;
&lt;p&gt;dm_dp_mst_is_port_support_mode() reads
aconnector-&amp;gt;dc_sink-&amp;gt;dsc_caps... for the DSC branch-throughput check,
and get_conv_frl_bw()&amp;#39;s HDMI-PCON FRL-bandwidth path reads
aconnector-&amp;gt;dc_sink-&amp;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&amp;#39;s own comments document as
racing that teardown: the connector probe worker&amp;#39;s -&amp;gt;mode_valid
callback and a compositor&amp;#39;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&amp;#39;t reliably cleared in
every path that clears dc_sink, so it doesn&amp;#39;t cover this.&lt;/p&gt;
&lt;p&gt;Fail the port-support check and skip the FRL conversion path when the
sink is already gone.&lt;/p&gt;
&lt;p&gt;(cherry picked from commit 7c3db8da4e039698ae198c870712428644e965c7)&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;drm/amd/display: guard dc_sink dereferences in MST mode validation&lt;/p&gt;
&lt;p&gt;dm_dp_mst_is_port_support_mode() reads
aconnector-&amp;gt;dc_sink-&amp;gt;dsc_caps... for the DSC branch-throughput check,
and get_conv_frl_bw()&amp;#39;s HDMI-PCON FRL-bandwidth path reads
aconnector-&amp;gt;dc_sink-&amp;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&amp;#39;s own comments document as
racing that teardown: the connector probe worker&amp;#39;s -&amp;gt;mode_valid
callback and a compositor&amp;#39;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&amp;#39;t reliably cleared in
every path that clears dc_sink, so it doesn&amp;#39;t cover this.&lt;/p&gt;
&lt;p&gt;Fail the port-support check and skip the FRL conversion path when the
sink is already gone.&lt;/p&gt;
&lt;p&gt;(cherry picked from commit 7c3db8da4e039698ae198c870712428644e965c7)&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ghsa-7r8j-xcf8-cxq6</guid>
    </item>
    <item>
      <title>msrc_CVE-2026-98786 — drm/amd/display: guard dc_sink dereferences in MST mode validation</title>
      <link>https://db.gcve.eu/vuln/msrc_cve-2026-98786</link>
      <description>msrc_CVE-2026-98786</description>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/msrc_cve-2026-98786</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-98786</title>
      <link>https://db.gcve.eu/vuln/ubuntu-cve-2026-98786</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3, Ubuntu:18.04:LTS: linux-gke-4.15, Ubuntu:18.04:LTS: linux-gke-5.4 and 155 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: drm/amd/display: guard dc_sink dereferences in MST mode validation dm_dp_mst_is_port_support_mode() reads aconnector-&amp;gt;dc_sink-&amp;gt;dsc_caps... for the DSC branch-throughput check, and get_conv_frl_bw()&amp;#39;s HDMI-PCON FRL-bandwidth path reads aconnector-&amp;gt;dc_sink-&amp;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&amp;#39;s own comments document as racing that teardown: the connector probe worker&amp;#39;s -&amp;gt;mode_valid callback and a compositor&amp;#39;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&amp;#39;t reliably cleared in every path that clears dc_sink, so it doesn&amp;#39;t cover this. Fail the port-support check and skip the FRL conversion path when the sink is already gone. (cherry picked from commit 7c3db8da4e039698ae198c870712428644e965c7)&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3, Ubuntu:18.04:LTS: linux-gke-4.15, Ubuntu:18.04:LTS: linux-gke-5.4 and 155 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: drm/amd/display: guard dc_sink dereferences in MST mode validation dm_dp_mst_is_port_support_mode() reads aconnector-&amp;gt;dc_sink-&amp;gt;dsc_caps... for the DSC branch-throughput check, and get_conv_frl_bw()&amp;#39;s HDMI-PCON FRL-bandwidth path reads aconnector-&amp;gt;dc_sink-&amp;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&amp;#39;s own comments document as racing that teardown: the connector probe worker&amp;#39;s -&amp;gt;mode_valid callback and a compositor&amp;#39;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&amp;#39;t reliably cleared in every path that clears dc_sink, so it doesn&amp;#39;t cover this. Fail the port-support check and skip the FRL conversion path when the sink is already gone. (cherry picked from commit 7c3db8da4e039698ae198c870712428644e965c7)&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ubuntu-cve-2026-98786</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-4019 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://db.gcve.eu/vuln/wid-sec-w-2026-4019</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen, möglicherweise einen Denial-of-Service-Angriff auszulösen, Daten zu manipulieren oder offenzulegen oder Sicherheitsmaßnahmen zu umgehen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen, möglicherweise einen Denial-of-Service-Angriff auszulösen, Daten zu manipulieren oder offenzulegen oder Sicherheitsmaßnahmen zu umgehen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/wid-sec-w-2026-4019</guid>
    </item>
  </channel>
</rss>
