<?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>Thu, 19 Nov 2026 23:56:30 +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>
    <item>
      <title>USN-9166-1 — linux, linux-aws, linux-gcp, linux-gcp-7.0, linux-gke, linux-ibm, linux-oem-7.0, linux-vmware vulnerabilities</title>
      <link>https://db.gcve.eu/vuln/usn-9166-1</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:24.04:LTS: linux-gcp-7.0, Ubuntu:26.04:LTS: linux, Ubuntu:26.04:LTS: linux-aws, Ubuntu:26.04:LTS: linux-gcp, Ubuntu:26.04:LTS: linux-gke, Ubuntu:26.04:LTS: linux-ibm, Ubuntu:26.04:LTS: linux-oem-7.0, Ubuntu:26.04:LTS: linux-vmware&lt;/p&gt;
&lt;p&gt;Several security issues were discovered in the Linux kernel.
An attacker could possibly use these to compromise the system.
This update corrects flaws in the following subsystems:
  - S390 architecture;
  - x86 architecture;
  - Block layer subsystem;
  - Cryptographic API;
  - Compute Acceleration Framework;
  - FireWire subsystem;
  - GPIO subsystem;
  - GPU drivers;
  - Microsoft Hyper-V drivers;
  - I2C subsystem;
  - Multiple devices driver;
  - Network drivers;
  - STMicroelectronics network drivers;
  - Power supply drivers;
  - S/390 drivers;
  - SCSI subsystem;
  - SPI subsystem;
  - TCM subsystem;
  - UFS subsystem;
  - File systems infrastructure;
  - Ext4 file system;
  - File system notification infrastructure;
  - NTFS3 file system;
  - OCFS2 file system;
  - SMB network file system;
  - Tracing file system;
  - XFS file system;
  - Kernel futex primitives;
  - Key management;
  - Key Management;
  - VMware vSockets driver;
  - io_uring subsystem;
  - IPC subsystem;
  - Perf events;
  - Kernel exit() syscall;
  - PID namespace;
  - printk logging mechanism;
  - Scheduler infrastructure;
  - Tracing infrastructure;
  - Watch queue notification mechanism;
  - Workqueue subsystem;
  - Ethernet bridge;
  - Networking core;
  - IPv4 networking;
  - IPv6 networking;
  - IUCV driver;
  - IEEE 802.15.4 subsystem;
  - Netfilter;
  - Netlink;
  - RDS protocol;
  - Network traffic control;
  - SCTP protocol;
  - TIPC protocol;
  - SELinux security module;
  - SOF drivers;…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:24.04:LTS: linux-gcp-7.0, Ubuntu:26.04:LTS: linux, Ubuntu:26.04:LTS: linux-aws, Ubuntu:26.04:LTS: linux-gcp, Ubuntu:26.04:LTS: linux-gke, Ubuntu:26.04:LTS: linux-ibm, Ubuntu:26.04:LTS: linux-oem-7.0, Ubuntu:26.04:LTS: linux-vmware&lt;/p&gt;
&lt;p&gt;Several security issues were discovered in the Linux kernel.
An attacker could possibly use these to compromise the system.
This update corrects flaws in the following subsystems:
  - S390 architecture;
  - x86 architecture;
  - Block layer subsystem;
  - Cryptographic API;
  - Compute Acceleration Framework;
  - FireWire subsystem;
  - GPIO subsystem;
  - GPU drivers;
  - Microsoft Hyper-V drivers;
  - I2C subsystem;
  - Multiple devices driver;
  - Network drivers;
  - STMicroelectronics network drivers;
  - Power supply drivers;
  - S/390 drivers;
  - SCSI subsystem;
  - SPI subsystem;
  - TCM subsystem;
  - UFS subsystem;
  - File systems infrastructure;
  - Ext4 file system;
  - File system notification infrastructure;
  - NTFS3 file system;
  - OCFS2 file system;
  - SMB network file system;
  - Tracing file system;
  - XFS file system;
  - Kernel futex primitives;
  - Key management;
  - Key Management;
  - VMware vSockets driver;
  - io_uring subsystem;
  - IPC subsystem;
  - Perf events;
  - Kernel exit() syscall;
  - PID namespace;
  - printk logging mechanism;
  - Scheduler infrastructure;
  - Tracing infrastructure;
  - Watch queue notification mechanism;
  - Workqueue subsystem;
  - Ethernet bridge;
  - Networking core;
  - IPv4 networking;
  - IPv6 networking;
  - IUCV driver;
  - IEEE 802.15.4 subsystem;
  - Netfilter;
  - Netlink;
  - RDS protocol;
  - Network traffic control;
  - SCTP protocol;
  - TIPC protocol;
  - SELinux security module;
  - SOF drivers;…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/usn-9166-1</guid>
    </item>
  </channel>
</rss>
