<?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>Fri, 02 Oct 2026 17:16:34 +0000</lastBuildDate>
    <item>
      <title>bdu:2026-11769</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2026-11769</link>
      <description>bdu:2026-11769</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2026-11769</guid>
    </item>
    <item>
      <title>BELL-CVE-2026-45890</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2026-45890</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:23: linux-lts, 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:23: linux-lts, Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bell-cve-2026-45890</guid>
    </item>
    <item>
      <title>certfr-2026-avi-0696 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de Debian LTS. Certaines d'entre elles permettent à…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2026-avi-0696</link>
      <description>certfr-2026-avi-0696</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2026-avi-0696</guid>
    </item>
    <item>
      <title>EUVD-2026-321812</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-321812</link>
      <description>EUVD-2026-321812</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-321812</guid>
    </item>
    <item>
      <title>fkie_cve-2026-45890</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-45890</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;xen-netback: reject zero-queue configuration from guest&lt;/p&gt;
&lt;p&gt;A malicious or buggy Xen guest can write &amp;#34;0&amp;#34; to the xenbus key
&amp;#34;multi-queue-num-queues&amp;#34;. The connect() function in the backend only
validates the upper bound (requested_num_queues &amp;gt; xenvif_max_queues)
but not zero, allowing requested_num_queues=0 to reach
vzalloc(array_size(0, sizeof(struct xenvif_queue))), which triggers
WARN_ON_ONCE(!size) in __vmalloc_node_range().&lt;/p&gt;
&lt;p&gt;On systems with panic_on_warn=1, this allows a guest-to-host denial
of service.&lt;/p&gt;
&lt;p&gt;The Xen network interface specification requires
the queue count to be &amp;#34;greater than zero&amp;#34;.&lt;/p&gt;
&lt;p&gt;Add a zero check to match the validation already present
in xen-blkback, which has included this
guard since its multi-queue support was added.&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;xen-netback: reject zero-queue configuration from guest&lt;/p&gt;
&lt;p&gt;A malicious or buggy Xen guest can write &amp;#34;0&amp;#34; to the xenbus key
&amp;#34;multi-queue-num-queues&amp;#34;. The connect() function in the backend only
validates the upper bound (requested_num_queues &amp;gt; xenvif_max_queues)
but not zero, allowing requested_num_queues=0 to reach
vzalloc(array_size(0, sizeof(struct xenvif_queue))), which triggers
WARN_ON_ONCE(!size) in __vmalloc_node_range().&lt;/p&gt;
&lt;p&gt;On systems with panic_on_warn=1, this allows a guest-to-host denial
of service.&lt;/p&gt;
&lt;p&gt;The Xen network interface specification requires
the queue count to be &amp;#34;greater than zero&amp;#34;.&lt;/p&gt;
&lt;p&gt;Add a zero check to match the validation already present
in xen-blkback, which has included this
guard since its multi-queue support was added.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-45890</guid>
    </item>
    <item>
      <title>GHSA-jc43-3m97-6p35</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-jc43-3m97-6p35</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;xen-netback: reject zero-queue configuration from guest&lt;/p&gt;
&lt;p&gt;A malicious or buggy Xen guest can write &amp;#34;0&amp;#34; to the xenbus key
&amp;#34;multi-queue-num-queues&amp;#34;. The connect() function in the backend only
validates the upper bound (requested_num_queues &amp;gt; xenvif_max_queues)
but not zero, allowing requested_num_queues=0 to reach
vzalloc(array_size(0, sizeof(struct xenvif_queue))), which triggers
WARN_ON_ONCE(!size) in __vmalloc_node_range().&lt;/p&gt;
&lt;p&gt;On systems with panic_on_warn=1, this allows a guest-to-host denial
of service.&lt;/p&gt;
&lt;p&gt;The Xen network interface specification requires
the queue count to be &amp;#34;greater than zero&amp;#34;.&lt;/p&gt;
&lt;p&gt;Add a zero check to match the validation already present
in xen-blkback, which has included this
guard since its multi-queue support was added.&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;xen-netback: reject zero-queue configuration from guest&lt;/p&gt;
&lt;p&gt;A malicious or buggy Xen guest can write &amp;#34;0&amp;#34; to the xenbus key
&amp;#34;multi-queue-num-queues&amp;#34;. The connect() function in the backend only
validates the upper bound (requested_num_queues &amp;gt; xenvif_max_queues)
but not zero, allowing requested_num_queues=0 to reach
vzalloc(array_size(0, sizeof(struct xenvif_queue))), which triggers
WARN_ON_ONCE(!size) in __vmalloc_node_range().&lt;/p&gt;
&lt;p&gt;On systems with panic_on_warn=1, this allows a guest-to-host denial
of service.&lt;/p&gt;
&lt;p&gt;The Xen network interface specification requires
the queue count to be &amp;#34;greater than zero&amp;#34;.&lt;/p&gt;
&lt;p&gt;Add a zero check to match the validation already present
in xen-blkback, which has included this
guard since its multi-queue support was added.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-jc43-3m97-6p35</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-45890</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-45890</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; 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, Ubuntu:16.04:LTS: linux-hwe-edge and 231 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: xen-netback: reject zero-queue configuration from guest A malicious or buggy Xen guest can write &amp;#34;0&amp;#34; to the xenbus key &amp;#34;multi-queue-num-queues&amp;#34;. The connect() function in the backend only validates the upper bound (requested_num_queues &amp;gt; xenvif_max_queues) but not zero, allowing requested_num_queues=0 to reach vzalloc(array_size(0, sizeof(struct xenvif_queue))), which triggers WARN_ON_ONCE(!size) in __vmalloc_node_range(). On systems with panic_on_warn=1, this allows a guest-to-host denial of service. The Xen network interface specification requires the queue count to be &amp;#34;greater than zero&amp;#34;. Add a zero check to match the validation already present in xen-blkback, which has included this guard since its multi-queue support was added.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; 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, Ubuntu:16.04:LTS: linux-hwe-edge and 231 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: xen-netback: reject zero-queue configuration from guest A malicious or buggy Xen guest can write &amp;#34;0&amp;#34; to the xenbus key &amp;#34;multi-queue-num-queues&amp;#34;. The connect() function in the backend only validates the upper bound (requested_num_queues &amp;gt; xenvif_max_queues) but not zero, allowing requested_num_queues=0 to reach vzalloc(array_size(0, sizeof(struct xenvif_queue))), which triggers WARN_ON_ONCE(!size) in __vmalloc_node_range(). On systems with panic_on_warn=1, this allows a guest-to-host denial of service. The Xen network interface specification requires the queue count to be &amp;#34;greater than zero&amp;#34;. Add a zero check to match the validation already present in xen-blkback, which has included this guard since its multi-queue support was added.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-45890</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-1700 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-1700</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen oder andere nicht näher spezifizierte 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 andere nicht näher spezifizierte Auswirkungen zu erzielen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2026-1700</guid>
    </item>
  </channel>
</rss>
