<?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://cve.radiocsirt.org</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>Sat, 03 Oct 2026 17:42:57 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2026-74440</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2026-74440</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bell-cve-2026-74440</guid>
    </item>
    <item>
      <title>certfr-2026-avi-1090 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de Debian. Elles permettent à un attaquant de provo…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2026-avi-1090</link>
      <description>certfr-2026-avi-1090</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2026-avi-1090</guid>
    </item>
    <item>
      <title>EUVD-2026-354234</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-354234</link>
      <description>EUVD-2026-354234</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-354234</guid>
    </item>
    <item>
      <title>fkie_cve-2026-74440</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-74440</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;drm/xe: Wait on external BO kernel fences in exec IOCTL&lt;/p&gt;
&lt;p&gt;Before arming a user job, xe_exec_ioctl() only added the VM&amp;#39;s
dma-resv KERNEL slot as a dependency. That slot covers rebinds and
the kernel operations of the VM&amp;#39;s private BOs, but not external BOs
(bo-&amp;gt;vm == NULL), which carry their kernel operations (evictions,
moves, ...) in their own dma-resv KERNEL slot.&lt;/p&gt;
&lt;p&gt;The DMA_RESV_USAGE_KERNEL slot is the cross-driver contract for
memory management operations that must complete before the BO or its
backing store may be used: any accessor is required to wait on the
KERNEL fences before touching the resv. By skipping the external BOs&amp;#39;
KERNEL slots, the exec path violated that contract and could schedule
a user job while a kernel operation on an external BO mapped by the VM
was still in flight, racing against it and potentially reading or
writing memory that was being moved.&lt;/p&gt;
&lt;p&gt;Replace the VM-only dependency with an iteration over every object
locked by the exec, adding each object&amp;#39;s KERNEL slot as a job
dependency. This covers the VM resv (rebinds and private BOs) as well
as every external BO, mirroring the drm_gpuvm_resv_add_fence() call
that later publishes the job fence to the same set of objects.
Long-running mode continues to skip this, as before.&lt;/p&gt;
&lt;p&gt;(cherry picked from commit a6b842acf3ddd1efc53a56de9260cfa718fb35e7)&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/xe: Wait on external BO kernel fences in exec IOCTL&lt;/p&gt;
&lt;p&gt;Before arming a user job, xe_exec_ioctl() only added the VM&amp;#39;s
dma-resv KERNEL slot as a dependency. That slot covers rebinds and
the kernel operations of the VM&amp;#39;s private BOs, but not external BOs
(bo-&amp;gt;vm == NULL), which carry their kernel operations (evictions,
moves, ...) in their own dma-resv KERNEL slot.&lt;/p&gt;
&lt;p&gt;The DMA_RESV_USAGE_KERNEL slot is the cross-driver contract for
memory management operations that must complete before the BO or its
backing store may be used: any accessor is required to wait on the
KERNEL fences before touching the resv. By skipping the external BOs&amp;#39;
KERNEL slots, the exec path violated that contract and could schedule
a user job while a kernel operation on an external BO mapped by the VM
was still in flight, racing against it and potentially reading or
writing memory that was being moved.&lt;/p&gt;
&lt;p&gt;Replace the VM-only dependency with an iteration over every object
locked by the exec, adding each object&amp;#39;s KERNEL slot as a job
dependency. This covers the VM resv (rebinds and private BOs) as well
as every external BO, mirroring the drm_gpuvm_resv_add_fence() call
that later publishes the job fence to the same set of objects.
Long-running mode continues to skip this, as before.&lt;/p&gt;
&lt;p&gt;(cherry picked from commit a6b842acf3ddd1efc53a56de9260cfa718fb35e7)&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-74440</guid>
    </item>
    <item>
      <title>GHSA-7mhj-6hx6-xpjh</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-7mhj-6hx6-xpjh</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;drm/xe: Wait on external BO kernel fences in exec IOCTL&lt;/p&gt;
&lt;p&gt;Before arming a user job, xe_exec_ioctl() only added the VM&amp;#39;s
dma-resv KERNEL slot as a dependency. That slot covers rebinds and
the kernel operations of the VM&amp;#39;s private BOs, but not external BOs
(bo-&amp;gt;vm == NULL), which carry their kernel operations (evictions,
moves, ...) in their own dma-resv KERNEL slot.&lt;/p&gt;
&lt;p&gt;The DMA_RESV_USAGE_KERNEL slot is the cross-driver contract for
memory management operations that must complete before the BO or its
backing store may be used: any accessor is required to wait on the
KERNEL fences before touching the resv. By skipping the external BOs&amp;#39;
KERNEL slots, the exec path violated that contract and could schedule
a user job while a kernel operation on an external BO mapped by the VM
was still in flight, racing against it and potentially reading or
writing memory that was being moved.&lt;/p&gt;
&lt;p&gt;Replace the VM-only dependency with an iteration over every object
locked by the exec, adding each object&amp;#39;s KERNEL slot as a job
dependency. This covers the VM resv (rebinds and private BOs) as well
as every external BO, mirroring the drm_gpuvm_resv_add_fence() call
that later publishes the job fence to the same set of objects.
Long-running mode continues to skip this, as before.&lt;/p&gt;
&lt;p&gt;(cherry picked from commit a6b842acf3ddd1efc53a56de9260cfa718fb35e7)&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/xe: Wait on external BO kernel fences in exec IOCTL&lt;/p&gt;
&lt;p&gt;Before arming a user job, xe_exec_ioctl() only added the VM&amp;#39;s
dma-resv KERNEL slot as a dependency. That slot covers rebinds and
the kernel operations of the VM&amp;#39;s private BOs, but not external BOs
(bo-&amp;gt;vm == NULL), which carry their kernel operations (evictions,
moves, ...) in their own dma-resv KERNEL slot.&lt;/p&gt;
&lt;p&gt;The DMA_RESV_USAGE_KERNEL slot is the cross-driver contract for
memory management operations that must complete before the BO or its
backing store may be used: any accessor is required to wait on the
KERNEL fences before touching the resv. By skipping the external BOs&amp;#39;
KERNEL slots, the exec path violated that contract and could schedule
a user job while a kernel operation on an external BO mapped by the VM
was still in flight, racing against it and potentially reading or
writing memory that was being moved.&lt;/p&gt;
&lt;p&gt;Replace the VM-only dependency with an iteration over every object
locked by the exec, adding each object&amp;#39;s KERNEL slot as a job
dependency. This covers the VM resv (rebinds and private BOs) as well
as every external BO, mirroring the drm_gpuvm_resv_add_fence() call
that later publishes the job fence to the same set of objects.
Long-running mode continues to skip this, as before.&lt;/p&gt;
&lt;p&gt;(cherry picked from commit a6b842acf3ddd1efc53a56de9260cfa718fb35e7)&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-7mhj-6hx6-xpjh</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-74440</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-74440</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 154 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: drm/xe: Wait on external BO kernel fences in exec IOCTL Before arming a user job, xe_exec_ioctl() only added the VM&amp;#39;s dma-resv KERNEL slot as a dependency. That slot covers rebinds and the kernel operations of the VM&amp;#39;s private BOs, but not external BOs (bo-&amp;gt;vm == NULL), which carry their kernel operations (evictions, moves, ...) in their own dma-resv KERNEL slot. The DMA_RESV_USAGE_KERNEL slot is the cross-driver contract for memory management operations that must complete before the BO or its backing store may be used: any accessor is required to wait on the KERNEL fences before touching the resv. By skipping the external BOs&amp;#39; KERNEL slots, the exec path violated that contract and could schedule a user job while a kernel operation on an external BO mapped by the VM was still in flight, racing against it and potentially reading or writing memory that was being moved. Replace the VM-only dependency with an iteration over every object locked by the exec, adding each object&amp;#39;s KERNEL slot as a job dependency. This covers the VM resv (rebinds and private BOs) as well as every external BO, mirroring the drm_gpuvm_resv_add_fence() call that later publishes the job fence to the same set of objects. Long-running mode continues to skip this, as before. (cherry picked from commit a6b842acf3ddd1efc53a56de9260cfa718fb35e7)&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 154 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: drm/xe: Wait on external BO kernel fences in exec IOCTL Before arming a user job, xe_exec_ioctl() only added the VM&amp;#39;s dma-resv KERNEL slot as a dependency. That slot covers rebinds and the kernel operations of the VM&amp;#39;s private BOs, but not external BOs (bo-&amp;gt;vm == NULL), which carry their kernel operations (evictions, moves, ...) in their own dma-resv KERNEL slot. The DMA_RESV_USAGE_KERNEL slot is the cross-driver contract for memory management operations that must complete before the BO or its backing store may be used: any accessor is required to wait on the KERNEL fences before touching the resv. By skipping the external BOs&amp;#39; KERNEL slots, the exec path violated that contract and could schedule a user job while a kernel operation on an external BO mapped by the VM was still in flight, racing against it and potentially reading or writing memory that was being moved. Replace the VM-only dependency with an iteration over every object locked by the exec, adding each object&amp;#39;s KERNEL slot as a job dependency. This covers the VM resv (rebinds and private BOs) as well as every external BO, mirroring the drm_gpuvm_resv_add_fence() call that later publishes the job fence to the same set of objects. Long-running mode continues to skip this, as before. (cherry picked from commit a6b842acf3ddd1efc53a56de9260cfa718fb35e7)&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-74440</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-2852 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-2852</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um root Rechte zu erlangen, um einen Denial of Service herbeizuführen oder einen nicht näher spezifizierten Angriff durchzuführen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um root Rechte zu erlangen, um einen Denial of Service herbeizuführen oder einen nicht näher spezifizierten Angriff durchzuführen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2026-2852</guid>
    </item>
  </channel>
</rss>
