<?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://vulnerability.circl.lu</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>Mon, 28 Sep 2026 15:59:41 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2026-93248</title>
      <link>https://vulnerability.circl.lu/vuln/bell-cve-2026-93248</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:stream: linux-lts&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:stream: linux-lts&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/bell-cve-2026-93248</guid>
    </item>
    <item>
      <title>fkie_cve-2026-93248</title>
      <link>https://vulnerability.circl.lu/vuln/fkie_cve-2026-93248</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;drm/xe: don&amp;#39;t WARN on kernel job timeout when device already wedged&lt;/p&gt;
&lt;p&gt;igt@xe_wedged@wedged-at-any-timeout wedges the device in mode 2
(UPON_ANY_HANG_NO_RESET) and then rebinds the driver. During unbind,
a GSC proxy kernel submission can still time out; with the device wedged
and the GuC CT stopped it can never complete, so its kernel job times out.&lt;/p&gt;
&lt;p&gt;Tile0: GT1: Kernel-submitted job timed out
  WARNING: drivers/gpu/drm/xe/xe_guc_submit.c:...
	   at guc_exec_queue_timedout_job()
  Workqueue: gt-ordered-wq drm_sched_job_timedout&lt;/p&gt;
&lt;p&gt;Killed queues skip guc_submit_hint_wedged(), leaving &amp;#39;wedged&amp;#39; false even
though the device is already wedged. The timeout handler then treats the
kernel queue timeout as unexpected and taints the kernel.&lt;/p&gt;
&lt;p&gt;Honour an already-wedged device even for killed queues so the expected
teardown timeout no longer trips the WARN.&lt;/p&gt;
&lt;p&gt;(cherry picked from commit a1c1dbd0f047bb05de6aaf6abe9103031179bf19)&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: don&amp;#39;t WARN on kernel job timeout when device already wedged&lt;/p&gt;
&lt;p&gt;igt@xe_wedged@wedged-at-any-timeout wedges the device in mode 2
(UPON_ANY_HANG_NO_RESET) and then rebinds the driver. During unbind,
a GSC proxy kernel submission can still time out; with the device wedged
and the GuC CT stopped it can never complete, so its kernel job times out.&lt;/p&gt;
&lt;p&gt;Tile0: GT1: Kernel-submitted job timed out
  WARNING: drivers/gpu/drm/xe/xe_guc_submit.c:...
	   at guc_exec_queue_timedout_job()
  Workqueue: gt-ordered-wq drm_sched_job_timedout&lt;/p&gt;
&lt;p&gt;Killed queues skip guc_submit_hint_wedged(), leaving &amp;#39;wedged&amp;#39; false even
though the device is already wedged. The timeout handler then treats the
kernel queue timeout as unexpected and taints the kernel.&lt;/p&gt;
&lt;p&gt;Honour an already-wedged device even for killed queues so the expected
teardown timeout no longer trips the WARN.&lt;/p&gt;
&lt;p&gt;(cherry picked from commit a1c1dbd0f047bb05de6aaf6abe9103031179bf19)&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/fkie_cve-2026-93248</guid>
    </item>
    <item>
      <title>GHSA-h35v-9854-jq4c</title>
      <link>https://vulnerability.circl.lu/vuln/ghsa-h35v-9854-jq4c</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;drm/xe: don&amp;#39;t WARN on kernel job timeout when device already wedged&lt;/p&gt;
&lt;p&gt;igt@xe_wedged@wedged-at-any-timeout wedges the device in mode 2
(UPON_ANY_HANG_NO_RESET) and then rebinds the driver. During unbind,
a GSC proxy kernel submission can still time out; with the device wedged
and the GuC CT stopped it can never complete, so its kernel job times out.&lt;/p&gt;
&lt;p&gt;Tile0: GT1: Kernel-submitted job timed out
  WARNING: drivers/gpu/drm/xe/xe_guc_submit.c:...
	   at guc_exec_queue_timedout_job()
  Workqueue: gt-ordered-wq drm_sched_job_timedout&lt;/p&gt;
&lt;p&gt;Killed queues skip guc_submit_hint_wedged(), leaving &amp;#39;wedged&amp;#39; false even
though the device is already wedged. The timeout handler then treats the
kernel queue timeout as unexpected and taints the kernel.&lt;/p&gt;
&lt;p&gt;Honour an already-wedged device even for killed queues so the expected
teardown timeout no longer trips the WARN.&lt;/p&gt;
&lt;p&gt;(cherry picked from commit a1c1dbd0f047bb05de6aaf6abe9103031179bf19)&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: don&amp;#39;t WARN on kernel job timeout when device already wedged&lt;/p&gt;
&lt;p&gt;igt@xe_wedged@wedged-at-any-timeout wedges the device in mode 2
(UPON_ANY_HANG_NO_RESET) and then rebinds the driver. During unbind,
a GSC proxy kernel submission can still time out; with the device wedged
and the GuC CT stopped it can never complete, so its kernel job times out.&lt;/p&gt;
&lt;p&gt;Tile0: GT1: Kernel-submitted job timed out
  WARNING: drivers/gpu/drm/xe/xe_guc_submit.c:...
	   at guc_exec_queue_timedout_job()
  Workqueue: gt-ordered-wq drm_sched_job_timedout&lt;/p&gt;
&lt;p&gt;Killed queues skip guc_submit_hint_wedged(), leaving &amp;#39;wedged&amp;#39; false even
though the device is already wedged. The timeout handler then treats the
kernel queue timeout as unexpected and taints the kernel.&lt;/p&gt;
&lt;p&gt;Honour an already-wedged device even for killed queues so the expected
teardown timeout no longer trips the WARN.&lt;/p&gt;
&lt;p&gt;(cherry picked from commit a1c1dbd0f047bb05de6aaf6abe9103031179bf19)&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ghsa-h35v-9854-jq4c</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-93248</title>
      <link>https://vulnerability.circl.lu/vuln/ubuntu-cve-2026-93248</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux, Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, Ubuntu:Pro:16.04:LTS: linux, Ubuntu:Pro:16.04:LTS: linux-aws, Ubuntu:Pro:16.04:LTS: linux-aws-hwe, Ubuntu:Pro:16.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-gcp, Ubuntu:Pro:16.04:LTS: linux-hwe and 246 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: drm/xe: don&amp;#39;t WARN on kernel job timeout when device already wedged igt@xe_wedged@wedged-at-any-timeout wedges the device in mode 2 (UPON_ANY_HANG_NO_RESET) and then rebinds the driver. During unbind, a GSC proxy kernel submission can still time out; with the device wedged and the GuC CT stopped it can never complete, so its kernel job times out.   Tile0: GT1: Kernel-submitted job timed out   WARNING: drivers/gpu/drm/xe/xe_guc_submit.c:... 	   at guc_exec_queue_timedout_job()   Workqueue: gt-ordered-wq drm_sched_job_timedout Killed queues skip guc_submit_hint_wedged(), leaving &amp;#39;wedged&amp;#39; false even though the device is already wedged. The timeout handler then treats the kernel queue timeout as unexpected and taints the kernel. Honour an already-wedged device even for killed queues so the expected teardown timeout no longer trips the WARN. (cherry picked from commit a1c1dbd0f047bb05de6aaf6abe9103031179bf19)&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux, Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, Ubuntu:Pro:16.04:LTS: linux, Ubuntu:Pro:16.04:LTS: linux-aws, Ubuntu:Pro:16.04:LTS: linux-aws-hwe, Ubuntu:Pro:16.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-gcp, Ubuntu:Pro:16.04:LTS: linux-hwe and 246 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: drm/xe: don&amp;#39;t WARN on kernel job timeout when device already wedged igt@xe_wedged@wedged-at-any-timeout wedges the device in mode 2 (UPON_ANY_HANG_NO_RESET) and then rebinds the driver. During unbind, a GSC proxy kernel submission can still time out; with the device wedged and the GuC CT stopped it can never complete, so its kernel job times out.   Tile0: GT1: Kernel-submitted job timed out   WARNING: drivers/gpu/drm/xe/xe_guc_submit.c:... 	   at guc_exec_queue_timedout_job()   Workqueue: gt-ordered-wq drm_sched_job_timedout Killed queues skip guc_submit_hint_wedged(), leaving &amp;#39;wedged&amp;#39; false even though the device is already wedged. The timeout handler then treats the kernel queue timeout as unexpected and taints the kernel. Honour an already-wedged device even for killed queues so the expected teardown timeout no longer trips the WARN. (cherry picked from commit a1c1dbd0f047bb05de6aaf6abe9103031179bf19)&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ubuntu-cve-2026-93248</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-3579 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://vulnerability.circl.lu/vuln/wid-sec-w-2026-3579</link>
      <description>&lt;p&gt;Ein lokaler Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Zustand herbeizuführen oder nicht näher spezifizierten Angriff durchzuführen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein lokaler Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Zustand herbeizuführen oder nicht näher spezifizierten Angriff durchzuführen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/wid-sec-w-2026-3579</guid>
    </item>
  </channel>
</rss>
