<?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>Sun, 04 Oct 2026 10:01:01 +0000</lastBuildDate>
    <item>
      <title>bdu:2026-12166</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2026-12166</link>
      <description>bdu:2026-12166</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2026-12166</guid>
    </item>
    <item>
      <title>BELL-CVE-2026-23354</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2026-23354</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-23354</guid>
    </item>
    <item>
      <title>certfr-2026-avi-0548 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de Debian. Certaines d'entre elles permettent à un…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2026-avi-0548</link>
      <description>certfr-2026-avi-0548</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2026-avi-0548</guid>
    </item>
    <item>
      <title>EUVD-2026-315495</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-315495</link>
      <description>EUVD-2026-315495</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-315495</guid>
    </item>
    <item>
      <title>fkie_cve-2026-23354</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-23354</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;x86/fred: Correct speculative safety in fred_extint()&lt;/p&gt;
&lt;p&gt;array_index_nospec() is no use if the result gets spilled to the stack, as
it makes the believed safe-under-speculation value subject to memory
predictions.&lt;/p&gt;
&lt;p&gt;For all practical purposes, this means array_index_nospec() must be used in
the expression that accesses the array.&lt;/p&gt;
&lt;p&gt;As the code currently stands, it&amp;#39;s the wrong side of irqentry_enter(), and
&amp;#39;index&amp;#39; is put into %ebp across the function call.&lt;/p&gt;
&lt;p&gt;Remove the index variable and reposition array_index_nospec(), so it&amp;#39;s
calculated immediately before the array access.&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;x86/fred: Correct speculative safety in fred_extint()&lt;/p&gt;
&lt;p&gt;array_index_nospec() is no use if the result gets spilled to the stack, as
it makes the believed safe-under-speculation value subject to memory
predictions.&lt;/p&gt;
&lt;p&gt;For all practical purposes, this means array_index_nospec() must be used in
the expression that accesses the array.&lt;/p&gt;
&lt;p&gt;As the code currently stands, it&amp;#39;s the wrong side of irqentry_enter(), and
&amp;#39;index&amp;#39; is put into %ebp across the function call.&lt;/p&gt;
&lt;p&gt;Remove the index variable and reposition array_index_nospec(), so it&amp;#39;s
calculated immediately before the array access.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-23354</guid>
    </item>
    <item>
      <title>GHSA-4jgp-jccm-6ppx</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-4jgp-jccm-6ppx</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;x86/fred: Correct speculative safety in fred_extint()&lt;/p&gt;
&lt;p&gt;array_index_nospec() is no use if the result gets spilled to the stack, as
it makes the believed safe-under-speculation value subject to memory
predictions.&lt;/p&gt;
&lt;p&gt;For all practical purposes, this means array_index_nospec() must be used in
the expression that accesses the array.&lt;/p&gt;
&lt;p&gt;As the code currently stands, it&amp;#39;s the wrong side of irqentry_enter(), and
&amp;#39;index&amp;#39; is put into %ebp across the function call.&lt;/p&gt;
&lt;p&gt;Remove the index variable and reposition array_index_nospec(), so it&amp;#39;s
calculated immediately before the array access.&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;x86/fred: Correct speculative safety in fred_extint()&lt;/p&gt;
&lt;p&gt;array_index_nospec() is no use if the result gets spilled to the stack, as
it makes the believed safe-under-speculation value subject to memory
predictions.&lt;/p&gt;
&lt;p&gt;For all practical purposes, this means array_index_nospec() must be used in
the expression that accesses the array.&lt;/p&gt;
&lt;p&gt;As the code currently stands, it&amp;#39;s the wrong side of irqentry_enter(), and
&amp;#39;index&amp;#39; is put into %ebp across the function call.&lt;/p&gt;
&lt;p&gt;Remove the index variable and reposition array_index_nospec(), so it&amp;#39;s
calculated immediately before the array access.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-4jgp-jccm-6ppx</guid>
    </item>
    <item>
      <title>openSUSE-SU-2026:20826-1 — Security update for the Linux Kernel</title>
      <link>https://cve.radiocsirt.org/vuln/opensuse-su-2026:20826-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:20826-1</guid>
    </item>
    <item>
      <title>SUSE-SU-2026:21834-1 — Security update for the Linux Kernel</title>
      <link>https://cve.radiocsirt.org/vuln/suse-su-2026:21834-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:21834-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-23354</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-23354</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: x86/fred: Correct speculative safety in fred_extint() array_index_nospec() is no use if the result gets spilled to the stack, as it makes the believed safe-under-speculation value subject to memory predictions. For all practical purposes, this means array_index_nospec() must be used in the expression that accesses the array. As the code currently stands, it&amp;#39;s the wrong side of irqentry_enter(), and &amp;#39;index&amp;#39; is put into %ebp across the function call. Remove the index variable and reposition array_index_nospec(), so it&amp;#39;s calculated immediately before the array access.&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: x86/fred: Correct speculative safety in fred_extint() array_index_nospec() is no use if the result gets spilled to the stack, as it makes the believed safe-under-speculation value subject to memory predictions. For all practical purposes, this means array_index_nospec() must be used in the expression that accesses the array. As the code currently stands, it&amp;#39;s the wrong side of irqentry_enter(), and &amp;#39;index&amp;#39; is put into %ebp across the function call. Remove the index variable and reposition array_index_nospec(), so it&amp;#39;s calculated immediately before the array access.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-23354</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-0861 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-0861</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um einen Denial of Service zu verursachen, Sicherheitsmaßnahmen zu umgehen, Informationen offenzulegen, weitere nicht spezifizierte Auswirkungen zu verursachen und potentiell Code auszuführen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um einen Denial of Service zu verursachen, Sicherheitsmaßnahmen zu umgehen, Informationen offenzulegen, weitere nicht spezifizierte Auswirkungen zu verursachen und potentiell Code auszuführen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2026-0861</guid>
    </item>
  </channel>
</rss>
