<?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, 10 Nov 2026 01:09:05 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-99151 — drm/amd/display: Fix NULL sink dereference in USB4 bandwidth functions</title>
      <link>https://db.gcve.eu/vuln/cve-2026-99151</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/amd/display: Fix NULL sink dereference in USB4 bandwidth functions&lt;/p&gt;
&lt;p&gt;allocate_usb4_bandwidth_for_stream() and allocate_usb4_bandwidth() both
use ASSERT(stream-&amp;gt;sink) before dereferencing stream-&amp;gt;sink-&amp;gt;link. ASSERT
is compiled out in production builds, so a NULL stream-&amp;gt;sink causes a
NULL pointer dereference.&lt;/p&gt;
&lt;p&gt;link_set_dpms_off() already guards two earlier accesses to stream-&amp;gt;sink
with explicit NULL checks, confirming that stream-&amp;gt;sink can legitimately
be NULL. The subsequent call to deallocate_usb4_bandwidth() had no
equivalent guard.&lt;/p&gt;
&lt;p&gt;Replace the ASSERT() calls with proper NULL checks that return false
early, and add a matching stream-&amp;gt;sink guard at the call site in
link_set_dpms_off() consistent with the surrounding pattern.&lt;/p&gt;
&lt;p&gt;v2: Keep the existing ASSERT() calls for diagnostics (to report
    unexpected NULL sink), and add explicit NULL checks that return false
    before dereferencing stream-&amp;gt;sink. Also add a matching stream-&amp;gt;sink
    guard at the deallocation call site in link_set_dpms_off(). (Alex)&lt;/p&gt;
&lt;p&gt;(cherry picked from commit 98029a0ce61feb52c563f65349dd9b25f672e355)&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/amd/display: Fix NULL sink dereference in USB4 bandwidth functions&lt;/p&gt;
&lt;p&gt;allocate_usb4_bandwidth_for_stream() and allocate_usb4_bandwidth() both
use ASSERT(stream-&amp;gt;sink) before dereferencing stream-&amp;gt;sink-&amp;gt;link. ASSERT
is compiled out in production builds, so a NULL stream-&amp;gt;sink causes a
NULL pointer dereference.&lt;/p&gt;
&lt;p&gt;link_set_dpms_off() already guards two earlier accesses to stream-&amp;gt;sink
with explicit NULL checks, confirming that stream-&amp;gt;sink can legitimately
be NULL. The subsequent call to deallocate_usb4_bandwidth() had no
equivalent guard.&lt;/p&gt;
&lt;p&gt;Replace the ASSERT() calls with proper NULL checks that return false
early, and add a matching stream-&amp;gt;sink guard at the call site in
link_set_dpms_off() consistent with the surrounding pattern.&lt;/p&gt;
&lt;p&gt;v2: Keep the existing ASSERT() calls for diagnostics (to report
    unexpected NULL sink), and add explicit NULL checks that return false
    before dereferencing stream-&amp;gt;sink. Also add a matching stream-&amp;gt;sink
    guard at the deallocation call site in link_set_dpms_off(). (Alex)&lt;/p&gt;
&lt;p&gt;(cherry picked from commit 98029a0ce61feb52c563f65349dd9b25f672e355)&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/cve-2026-99151</guid>
    </item>
  </channel>
</rss>
