<?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:53:14 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2026-89590</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2026-89590</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://cve.radiocsirt.org/vuln/bell-cve-2026-89590</guid>
    </item>
    <item>
      <title>EUVD-2026-367021</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-367021</link>
      <description>EUVD-2026-367021</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-367021</guid>
    </item>
    <item>
      <title>fkie_cve-2026-89590</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-89590</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;accel/rocket: Fix error path handling in rocket_job_run()&lt;/p&gt;
&lt;p&gt;In rocket_job_run(), after taking an extra fence reference for
job-&amp;gt;done_fence via dma_fence_get(), the error paths have three bugs:&lt;/p&gt;
&lt;p&gt;- The dma_fence reference held by job-&amp;gt;done_fence is never released,
  causing a reference leak.
- pm_runtime_get_sync() increments the usage counter even on failure,
  but the error path does not decrement it, leaking the runtime PM
  reference and preventing the NPU from suspending.
- A valid but unsignaled fence is returned to the DRM scheduler,
  which triggers WARN(&amp;#34;Fence ... released with pending signals!&amp;#34;)
  when the scheduler drops its reference.&lt;/p&gt;
&lt;p&gt;Fix by replacing pm_runtime_get_sync() with pm_runtime_resume_and_get()
which auto-balances the usage counter on failure, releasing both fence
references on error, and returning ERR_PTR(ret) instead of the
unsignaled fence.&lt;/p&gt;
&lt;p&gt;[tomeu: Refactored error paths to use consolidated goto labels]&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;accel/rocket: Fix error path handling in rocket_job_run()&lt;/p&gt;
&lt;p&gt;In rocket_job_run(), after taking an extra fence reference for
job-&amp;gt;done_fence via dma_fence_get(), the error paths have three bugs:&lt;/p&gt;
&lt;p&gt;- The dma_fence reference held by job-&amp;gt;done_fence is never released,
  causing a reference leak.
- pm_runtime_get_sync() increments the usage counter even on failure,
  but the error path does not decrement it, leaking the runtime PM
  reference and preventing the NPU from suspending.
- A valid but unsignaled fence is returned to the DRM scheduler,
  which triggers WARN(&amp;#34;Fence ... released with pending signals!&amp;#34;)
  when the scheduler drops its reference.&lt;/p&gt;
&lt;p&gt;Fix by replacing pm_runtime_get_sync() with pm_runtime_resume_and_get()
which auto-balances the usage counter on failure, releasing both fence
references on error, and returning ERR_PTR(ret) instead of the
unsignaled fence.&lt;/p&gt;
&lt;p&gt;[tomeu: Refactored error paths to use consolidated goto labels]&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-89590</guid>
    </item>
    <item>
      <title>GHSA-8m8f-887v-xxcc</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-8m8f-887v-xxcc</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;accel/rocket: Fix error path handling in rocket_job_run()&lt;/p&gt;
&lt;p&gt;In rocket_job_run(), after taking an extra fence reference for
job-&amp;gt;done_fence via dma_fence_get(), the error paths have three bugs:&lt;/p&gt;
&lt;p&gt;- The dma_fence reference held by job-&amp;gt;done_fence is never released,
  causing a reference leak.
- pm_runtime_get_sync() increments the usage counter even on failure,
  but the error path does not decrement it, leaking the runtime PM
  reference and preventing the NPU from suspending.
- A valid but unsignaled fence is returned to the DRM scheduler,
  which triggers WARN(&amp;#34;Fence ... released with pending signals!&amp;#34;)
  when the scheduler drops its reference.&lt;/p&gt;
&lt;p&gt;Fix by replacing pm_runtime_get_sync() with pm_runtime_resume_and_get()
which auto-balances the usage counter on failure, releasing both fence
references on error, and returning ERR_PTR(ret) instead of the
unsignaled fence.&lt;/p&gt;
&lt;p&gt;[tomeu: Refactored error paths to use consolidated goto labels]&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;accel/rocket: Fix error path handling in rocket_job_run()&lt;/p&gt;
&lt;p&gt;In rocket_job_run(), after taking an extra fence reference for
job-&amp;gt;done_fence via dma_fence_get(), the error paths have three bugs:&lt;/p&gt;
&lt;p&gt;- The dma_fence reference held by job-&amp;gt;done_fence is never released,
  causing a reference leak.
- pm_runtime_get_sync() increments the usage counter even on failure,
  but the error path does not decrement it, leaking the runtime PM
  reference and preventing the NPU from suspending.
- A valid but unsignaled fence is returned to the DRM scheduler,
  which triggers WARN(&amp;#34;Fence ... released with pending signals!&amp;#34;)
  when the scheduler drops its reference.&lt;/p&gt;
&lt;p&gt;Fix by replacing pm_runtime_get_sync() with pm_runtime_resume_and_get()
which auto-balances the usage counter on failure, releasing both fence
references on error, and returning ERR_PTR(ret) instead of the
unsignaled fence.&lt;/p&gt;
&lt;p&gt;[tomeu: Refactored error paths to use consolidated goto labels]&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-8m8f-887v-xxcc</guid>
    </item>
    <item>
      <title>openSUSE-SU-2026:11880-1 — kernel-devel-7.2.7-1.1 on GA media</title>
      <link>https://cve.radiocsirt.org/vuln/opensuse-su-2026:11880-1</link>
      <description>&lt;p&gt;kernel-devel-7.2.7-1.1 on GA media&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;kernel-devel-7.2.7-1.1 on GA media&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/opensuse-su-2026:11880-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-89590</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-89590</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 118 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: accel/rocket: Fix error path handling in rocket_job_run() In rocket_job_run(), after taking an extra fence reference for job-&amp;gt;done_fence via dma_fence_get(), the error paths have three bugs: - The dma_fence reference held by job-&amp;gt;done_fence is never released,   causing a reference leak. - pm_runtime_get_sync() increments the usage counter even on failure,   but the error path does not decrement it, leaking the runtime PM   reference and preventing the NPU from suspending. - A valid but unsignaled fence is returned to the DRM scheduler,   which triggers WARN(&amp;#34;Fence ... released with pending signals!&amp;#34;)   when the scheduler drops its reference. Fix by replacing pm_runtime_get_sync() with pm_runtime_resume_and_get() which auto-balances the usage counter on failure, releasing both fence references on error, and returning ERR_PTR(ret) instead of the unsignaled fence. [tomeu: Refactored error paths to use consolidated goto labels]&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 118 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: accel/rocket: Fix error path handling in rocket_job_run() In rocket_job_run(), after taking an extra fence reference for job-&amp;gt;done_fence via dma_fence_get(), the error paths have three bugs: - The dma_fence reference held by job-&amp;gt;done_fence is never released,   causing a reference leak. - pm_runtime_get_sync() increments the usage counter even on failure,   but the error path does not decrement it, leaking the runtime PM   reference and preventing the NPU from suspending. - A valid but unsignaled fence is returned to the DRM scheduler,   which triggers WARN(&amp;#34;Fence ... released with pending signals!&amp;#34;)   when the scheduler drops its reference. Fix by replacing pm_runtime_get_sync() with pm_runtime_resume_and_get() which auto-balances the usage counter on failure, releasing both fence references on error, and returning ERR_PTR(ret) instead of the unsignaled fence. [tomeu: Refactored error paths to use consolidated goto labels]&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-89590</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-3321 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-3321</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um Sicherheitsmaßnahmen zu umgehen, Daten oder den Systemzustand zu manipulieren, Denial-of-Service-Zustände herbeizuführen oder andere, nicht näher spezifizierte Angriffe durchzuführen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um Sicherheitsmaßnahmen zu umgehen, Daten oder den Systemzustand zu manipulieren, Denial-of-Service-Zustände herbeizuführen oder andere, nicht näher spezifizierte Angriffe durchzuführen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2026-3321</guid>
    </item>
  </channel>
</rss>
