<?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 17:29:03 +0000</lastBuildDate>
    <item>
      <title>CVE-2025-21880 — drm/xe/userptr: fix EFAULT handling</title>
      <link>https://db.gcve.eu/vuln/cve-2025-21880</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/userptr: fix EFAULT handling&lt;/p&gt;
&lt;p&gt;Currently we treat EFAULT from hmm_range_fault() as a non-fatal error
when called from xe_vm_userptr_pin() with the idea that we want to avoid
killing the entire vm and chucking an error, under the assumption that
the user just did an unmap or something, and has no intention of
actually touching that memory from the GPU.  At this point we have
already zapped the PTEs so any access should generate a page fault, and
if the pin fails there also it will then become fatal.&lt;/p&gt;
&lt;p&gt;However it looks like it&amp;#39;s possible for the userptr vma to still be on
the rebind list in preempt_rebind_work_func(), if we had to retry the
pin again due to something happening in the caller before we did the
rebind step, but in the meantime needing to re-validate the userptr and
this time hitting the EFAULT.&lt;/p&gt;
&lt;p&gt;This explains an internal user report of hitting:&lt;/p&gt;
&lt;p&gt;[  191.738349] WARNING: CPU: 1 PID: 157 at drivers/gpu/drm/xe/xe_res_cursor.h:158 xe_pt_stage_bind.constprop.0+0x60a/0x6b0 [xe]
[  191.738551] Workqueue: xe-ordered-wq preempt_rebind_work_func [xe]
[  191.738616] RIP: 0010:xe_pt_stage_bind.constprop.0+0x60a/0x6b0 [xe]
[  191.738690] Call Trace:
[  191.738692]  &amp;lt;TASK&amp;gt;
[  191.738694]  ? show_regs+0x69/0x80
[  191.738698]  ? __warn+0x93/0x1a0
[  191.738703]  ? xe_pt_stage_bind.constprop.0+0x60a/0x6b0 [xe]
[  191.738759]  ? report_bug+0x18f/0x1a0
[  191.738764]  ? handle_bug+0x63/0xa0
[  191.738767]  ?…&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/userptr: fix EFAULT handling&lt;/p&gt;
&lt;p&gt;Currently we treat EFAULT from hmm_range_fault() as a non-fatal error
when called from xe_vm_userptr_pin() with the idea that we want to avoid
killing the entire vm and chucking an error, under the assumption that
the user just did an unmap or something, and has no intention of
actually touching that memory from the GPU.  At this point we have
already zapped the PTEs so any access should generate a page fault, and
if the pin fails there also it will then become fatal.&lt;/p&gt;
&lt;p&gt;However it looks like it&amp;#39;s possible for the userptr vma to still be on
the rebind list in preempt_rebind_work_func(), if we had to retry the
pin again due to something happening in the caller before we did the
rebind step, but in the meantime needing to re-validate the userptr and
this time hitting the EFAULT.&lt;/p&gt;
&lt;p&gt;This explains an internal user report of hitting:&lt;/p&gt;
&lt;p&gt;[  191.738349] WARNING: CPU: 1 PID: 157 at drivers/gpu/drm/xe/xe_res_cursor.h:158 xe_pt_stage_bind.constprop.0+0x60a/0x6b0 [xe]
[  191.738551] Workqueue: xe-ordered-wq preempt_rebind_work_func [xe]
[  191.738616] RIP: 0010:xe_pt_stage_bind.constprop.0+0x60a/0x6b0 [xe]
[  191.738690] Call Trace:
[  191.738692]  &amp;lt;TASK&amp;gt;
[  191.738694]  ? show_regs+0x69/0x80
[  191.738698]  ? __warn+0x93/0x1a0
[  191.738703]  ? xe_pt_stage_bind.constprop.0+0x60a/0x6b0 [xe]
[  191.738759]  ? report_bug+0x18f/0x1a0
[  191.738764]  ? handle_bug+0x63/0xa0
[  191.738767]  ?…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/cve-2025-21880</guid>
    </item>
    <item>
      <title>USN-7764-1 — linux, linux-aws, linux-gcp, linux-gke, linux-gkeop, linux-lowlatency, linux-lowlatency-hwe-6.8 vulnerabilities</title>
      <link>https://db.gcve.eu/vuln/usn-7764-1</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:22.04:LTS: linux-lowlatency-hwe-6.8, Ubuntu:24.04:LTS: linux, Ubuntu:24.04:LTS: linux-aws, Ubuntu:24.04:LTS: linux-gcp, Ubuntu:24.04:LTS: linux-gke, Ubuntu:24.04:LTS: linux-gkeop, Ubuntu:24.04:LTS: linux-lowlatency&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:
  - ARM32 architecture;
  - ARM64 architecture;
  - x86 architecture;
  - Compute Acceleration Framework;
  - Bus devices;
  - AMD CDX bus driver;
  - DPLL subsystem;
  - EFI core;
  - GPIO subsystem;
  - GPU drivers;
  - HID subsystem;
  - I2C subsystem;
  - InfiniBand drivers;
  - Multiple devices driver;
  - Network drivers;
  - Mellanox network drivers;
  - NVME drivers;
  - Pin controllers subsystem;
  - RapidIO drivers;
  - Voltage and Current Regulator drivers;
  - SCSI subsystem;
  - SLIMbus drivers;
  - QCOM SoC drivers;
  - UFS subsystem;
  - USB DSL drivers;
  - Renesas USBHS Controller drivers;
  - USB Type-C Connector System Software Interface driver;
  - Framebuffer layer;
  - ACRN Hypervisor Service Module driver;
  - Network file system (NFS) client;
  - Proc file system;
  - SMB network file system;
  - Memory Management;
  - Scheduler infrastructure;
  - SoC audio core drivers;
  - Perf events;
  - Tracing infrastructure;
  - Memory management;
  - 802.1Q VLAN protocol;
  - Asynchronous Transfer Mode (ATM) subsystem;
  - Bluetooth subsystem;
  - Devlink API;
  - IPv4 networking;
  - IPv6 networking;
  - Logical Link layer;
  - Management Component Transport Protocol (MCTP);
  - Multipath TCP;
  - Netfilter;
  - Network traffic control;
  - Switch device API;
  - Wireless networkin…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:22.04:LTS: linux-lowlatency-hwe-6.8, Ubuntu:24.04:LTS: linux, Ubuntu:24.04:LTS: linux-aws, Ubuntu:24.04:LTS: linux-gcp, Ubuntu:24.04:LTS: linux-gke, Ubuntu:24.04:LTS: linux-gkeop, Ubuntu:24.04:LTS: linux-lowlatency&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:
  - ARM32 architecture;
  - ARM64 architecture;
  - x86 architecture;
  - Compute Acceleration Framework;
  - Bus devices;
  - AMD CDX bus driver;
  - DPLL subsystem;
  - EFI core;
  - GPIO subsystem;
  - GPU drivers;
  - HID subsystem;
  - I2C subsystem;
  - InfiniBand drivers;
  - Multiple devices driver;
  - Network drivers;
  - Mellanox network drivers;
  - NVME drivers;
  - Pin controllers subsystem;
  - RapidIO drivers;
  - Voltage and Current Regulator drivers;
  - SCSI subsystem;
  - SLIMbus drivers;
  - QCOM SoC drivers;
  - UFS subsystem;
  - USB DSL drivers;
  - Renesas USBHS Controller drivers;
  - USB Type-C Connector System Software Interface driver;
  - Framebuffer layer;
  - ACRN Hypervisor Service Module driver;
  - Network file system (NFS) client;
  - Proc file system;
  - SMB network file system;
  - Memory Management;
  - Scheduler infrastructure;
  - SoC audio core drivers;
  - Perf events;
  - Tracing infrastructure;
  - Memory management;
  - 802.1Q VLAN protocol;
  - Asynchronous Transfer Mode (ATM) subsystem;
  - Bluetooth subsystem;
  - Devlink API;
  - IPv4 networking;
  - IPv6 networking;
  - Logical Link layer;
  - Management Component Transport Protocol (MCTP);
  - Multipath TCP;
  - Netfilter;
  - Network traffic control;
  - Switch device API;
  - Wireless networkin…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/usn-7764-1</guid>
    </item>
  </channel>
</rss>
