<?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:35 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-99209 — drm/xe: skip eviction of a BO with no resource</title>
      <link>https://db.gcve.eu/vuln/cve-2026-99209</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/xe: skip eviction of a BO with no resource&lt;/p&gt;
&lt;p&gt;xe_evict_flags() switches on tbo-&amp;gt;resource-&amp;gt;mem_type to choose an
eviction placement. An xe BO can reach eviction with no ttm.resource,
e.g. an imported dma-buf BO whose resource was freed during teardown
while its attachment is still live: the exporter then invalidates it via
xe_dma_buf_move_notify() -&amp;gt; xe_bo_evict(), and the switch dereferences a
NULL resource and faults.&lt;/p&gt;
&lt;p&gt;A BO with no resource has nothing placed or mapped, so there is nothing
to evict. Return an empty placement (num_placement = 0), mirroring the
handling already used for non-xe scatter-gather BOs just above;
ttm_bo_validate() then takes the pipeline-gutting path and returns 0.&lt;/p&gt;
&lt;p&gt;Without the fix the xe_dma_buf@xe_test_dmabuf_move_notify_no_resource
dynamic live selftest will fail with below stack.&lt;/p&gt;
&lt;p&gt;BUG: kernel NULL pointer dereference, address: 0000000000000010
RIP: 0010:xe_evict_flags+0xf4/0x140 [xe]
Call Trace:
 &amp;lt;TASK&amp;gt;
 xe_bo_evict+0x40/0xa0 [xe]
 ? ttm_bo_pipeline_gutting+0x71/0x180 [ttm]
 xe_test_dmabuf_move_notify_no_resource+0x182/0x440 [xe]
 xe_dma_buf_kunit+0x387/0x580 [xe]&lt;/p&gt;
&lt;p&gt;v2: Add Fixes tag and failure info in commit text (Matt Brost)&lt;/p&gt;
&lt;p&gt;(cherry picked from commit dbcfaac6331f1fcb0c2fe3ad3e9adb1e5d43ec0c)&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/xe: skip eviction of a BO with no resource&lt;/p&gt;
&lt;p&gt;xe_evict_flags() switches on tbo-&amp;gt;resource-&amp;gt;mem_type to choose an
eviction placement. An xe BO can reach eviction with no ttm.resource,
e.g. an imported dma-buf BO whose resource was freed during teardown
while its attachment is still live: the exporter then invalidates it via
xe_dma_buf_move_notify() -&amp;gt; xe_bo_evict(), and the switch dereferences a
NULL resource and faults.&lt;/p&gt;
&lt;p&gt;A BO with no resource has nothing placed or mapped, so there is nothing
to evict. Return an empty placement (num_placement = 0), mirroring the
handling already used for non-xe scatter-gather BOs just above;
ttm_bo_validate() then takes the pipeline-gutting path and returns 0.&lt;/p&gt;
&lt;p&gt;Without the fix the xe_dma_buf@xe_test_dmabuf_move_notify_no_resource
dynamic live selftest will fail with below stack.&lt;/p&gt;
&lt;p&gt;BUG: kernel NULL pointer dereference, address: 0000000000000010
RIP: 0010:xe_evict_flags+0xf4/0x140 [xe]
Call Trace:
 &amp;lt;TASK&amp;gt;
 xe_bo_evict+0x40/0xa0 [xe]
 ? ttm_bo_pipeline_gutting+0x71/0x180 [ttm]
 xe_test_dmabuf_move_notify_no_resource+0x182/0x440 [xe]
 xe_dma_buf_kunit+0x387/0x580 [xe]&lt;/p&gt;
&lt;p&gt;v2: Add Fixes tag and failure info in commit text (Matt Brost)&lt;/p&gt;
&lt;p&gt;(cherry picked from commit dbcfaac6331f1fcb0c2fe3ad3e9adb1e5d43ec0c)&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/cve-2026-99209</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>
