<?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>Mon, 05 Oct 2026 10:45:14 +0000</lastBuildDate>
    <item>
      <title>bdu:2026-12039</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2026-12039</link>
      <description>bdu:2026-12039</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2026-12039</guid>
    </item>
    <item>
      <title>BELL-CVE-2025-71314</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2025-71314</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-2025-71314</guid>
    </item>
    <item>
      <title>certfr-2026-avi-0927 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de SUSE. Certaines d'entre elles permettent à un at…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2026-avi-0927</link>
      <description>certfr-2026-avi-0927</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2026-avi-0927</guid>
    </item>
    <item>
      <title>EUVD-2026-324413</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-324413</link>
      <description>EUVD-2026-324413</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-324413</guid>
    </item>
    <item>
      <title>fkie_cve-2025-71314</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2025-71314</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;drm/panthor: Recover from panthor_gpu_flush_caches() failures&lt;/p&gt;
&lt;p&gt;We have seen a few cases where the whole memory subsystem is blocked
and flush operations never complete. When that happens, we want to:&lt;/p&gt;
&lt;p&gt;- schedule a reset, so we can recover from this situation
- in the reset path, we need to reset the pending_reqs so we can send
  new commands after the reset
- if more panthor_gpu_flush_caches() operations are queued after
  the timeout, we skip them and return -EIO directly to avoid needless
  waits (the memory block won&amp;#39;t miraculously work again)&lt;/p&gt;
&lt;p&gt;Note that we drop the WARN_ON()s because these hangs can be triggered
with buggy GPU jobs created by the UMD, and there&amp;#39;s no way we can
prevent it. We do keep the error messages though.&lt;/p&gt;
&lt;p&gt;v2:
- New patch&lt;/p&gt;
&lt;p&gt;v3:
- Collect R-b
- Explicitly mention the fact we dropped the WARN_ON()s in the commit
  message&lt;/p&gt;
&lt;p&gt;v4:
- No changes&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/panthor: Recover from panthor_gpu_flush_caches() failures&lt;/p&gt;
&lt;p&gt;We have seen a few cases where the whole memory subsystem is blocked
and flush operations never complete. When that happens, we want to:&lt;/p&gt;
&lt;p&gt;- schedule a reset, so we can recover from this situation
- in the reset path, we need to reset the pending_reqs so we can send
  new commands after the reset
- if more panthor_gpu_flush_caches() operations are queued after
  the timeout, we skip them and return -EIO directly to avoid needless
  waits (the memory block won&amp;#39;t miraculously work again)&lt;/p&gt;
&lt;p&gt;Note that we drop the WARN_ON()s because these hangs can be triggered
with buggy GPU jobs created by the UMD, and there&amp;#39;s no way we can
prevent it. We do keep the error messages though.&lt;/p&gt;
&lt;p&gt;v2:
- New patch&lt;/p&gt;
&lt;p&gt;v3:
- Collect R-b
- Explicitly mention the fact we dropped the WARN_ON()s in the commit
  message&lt;/p&gt;
&lt;p&gt;v4:
- No changes&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2025-71314</guid>
    </item>
    <item>
      <title>GHSA-7rv6-jm8q-x9p7</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-7rv6-jm8q-x9p7</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;drm/panthor: Recover from panthor_gpu_flush_caches() failures&lt;/p&gt;
&lt;p&gt;We have seen a few cases where the whole memory subsystem is blocked
and flush operations never complete. When that happens, we want to:&lt;/p&gt;
&lt;p&gt;- schedule a reset, so we can recover from this situation
- in the reset path, we need to reset the pending_reqs so we can send
  new commands after the reset
- if more panthor_gpu_flush_caches() operations are queued after
  the timeout, we skip them and return -EIO directly to avoid needless
  waits (the memory block won&amp;#39;t miraculously work again)&lt;/p&gt;
&lt;p&gt;Note that we drop the WARN_ON()s because these hangs can be triggered
with buggy GPU jobs created by the UMD, and there&amp;#39;s no way we can
prevent it. We do keep the error messages though.&lt;/p&gt;
&lt;p&gt;v2:
- New patch&lt;/p&gt;
&lt;p&gt;v3:
- Collect R-b
- Explicitly mention the fact we dropped the WARN_ON()s in the commit
  message&lt;/p&gt;
&lt;p&gt;v4:
- No changes&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/panthor: Recover from panthor_gpu_flush_caches() failures&lt;/p&gt;
&lt;p&gt;We have seen a few cases where the whole memory subsystem is blocked
and flush operations never complete. When that happens, we want to:&lt;/p&gt;
&lt;p&gt;- schedule a reset, so we can recover from this situation
- in the reset path, we need to reset the pending_reqs so we can send
  new commands after the reset
- if more panthor_gpu_flush_caches() operations are queued after
  the timeout, we skip them and return -EIO directly to avoid needless
  waits (the memory block won&amp;#39;t miraculously work again)&lt;/p&gt;
&lt;p&gt;Note that we drop the WARN_ON()s because these hangs can be triggered
with buggy GPU jobs created by the UMD, and there&amp;#39;s no way we can
prevent it. We do keep the error messages though.&lt;/p&gt;
&lt;p&gt;v2:
- New patch&lt;/p&gt;
&lt;p&gt;v3:
- Collect R-b
- Explicitly mention the fact we dropped the WARN_ON()s in the commit
  message&lt;/p&gt;
&lt;p&gt;v4:
- No changes&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-7rv6-jm8q-x9p7</guid>
    </item>
    <item>
      <title>openSUSE-SU-2026:21555-1 — Security update for the Linux Kernel</title>
      <link>https://cve.radiocsirt.org/vuln/opensuse-su-2026:21555-1</link>
      <description>&lt;p&gt;Security update for the Linux Kernel&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Security update for the Linux Kernel&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/opensuse-su-2026:21555-1</guid>
    </item>
    <item>
      <title>SUSE-SU-2026:23066-1 — Security update for the Linux Kernel</title>
      <link>https://cve.radiocsirt.org/vuln/suse-su-2026:23066-1</link>
      <description>&lt;p&gt;Security update for the Linux Kernel&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Security update for the Linux Kernel&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/suse-su-2026:23066-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2025-71314</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-71314</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 106 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: drm/panthor: Recover from panthor_gpu_flush_caches() failures We have seen a few cases where the whole memory subsystem is blocked and flush operations never complete. When that happens, we want to: - schedule a reset, so we can recover from this situation - in the reset path, we need to reset the pending_reqs so we can send   new commands after the reset - if more panthor_gpu_flush_caches() operations are queued after   the timeout, we skip them and return -EIO directly to avoid needless   waits (the memory block won&amp;#39;t miraculously work again) Note that we drop the WARN_ON()s because these hangs can be triggered with buggy GPU jobs created by the UMD, and there&amp;#39;s no way we can prevent it. We do keep the error messages though. v2: - New patch v3: - Collect R-b - Explicitly mention the fact we dropped the WARN_ON()s in the commit   message v4: - No changes&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 106 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: drm/panthor: Recover from panthor_gpu_flush_caches() failures We have seen a few cases where the whole memory subsystem is blocked and flush operations never complete. When that happens, we want to: - schedule a reset, so we can recover from this situation - in the reset path, we need to reset the pending_reqs so we can send   new commands after the reset - if more panthor_gpu_flush_caches() operations are queued after   the timeout, we skip them and return -EIO directly to avoid needless   waits (the memory block won&amp;#39;t miraculously work again) Note that we drop the WARN_ON()s because these hangs can be triggered with buggy GPU jobs created by the UMD, and there&amp;#39;s no way we can prevent it. We do keep the error messages though. v2: - New patch v3: - Collect R-b - Explicitly mention the fact we dropped the WARN_ON()s in the commit   message v4: - No changes&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-71314</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-1802 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-1802</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen oder nicht bekannte Auswirkungen zu erzielen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen oder nicht bekannte Auswirkungen zu erzielen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2026-1802</guid>
    </item>
  </channel>
</rss>
