<?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 14:32:21 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2026-80858</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2026-80858</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-80858</guid>
    </item>
    <item>
      <title>EUVD-2026-366716</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-366716</link>
      <description>EUVD-2026-366716</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-366716</guid>
    </item>
    <item>
      <title>fkie_cve-2026-80858</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-80858</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;fuse: publish io-uring queues with release semantics&lt;/p&gt;
&lt;p&gt;fuse_uring_create_queue() initializes a fuse_ring_queue and then
publishes the pointer into ring-&amp;gt;queues[qid] with WRITE_ONCE() under the
fch-&amp;gt;lock. There are several readers that may concurrently be fetching
that pointer locklessly and then deferencing it.&lt;/p&gt;
&lt;p&gt;WRITE_ONCE() doesn&amp;#39;t ensure ordering of the queue&amp;#39;s field
initialization before the ring-&amp;gt;queues[qid] pointer assignment. The
queue must be published with smp_store_release() so the field
initialization is guaranteed to happen before.&lt;/p&gt;
&lt;p&gt;Readers in paths where the read may happen concurrently with the store
need to use READ_ONCE() because any race involving a plain access is
undefined.&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;fuse: publish io-uring queues with release semantics&lt;/p&gt;
&lt;p&gt;fuse_uring_create_queue() initializes a fuse_ring_queue and then
publishes the pointer into ring-&amp;gt;queues[qid] with WRITE_ONCE() under the
fch-&amp;gt;lock. There are several readers that may concurrently be fetching
that pointer locklessly and then deferencing it.&lt;/p&gt;
&lt;p&gt;WRITE_ONCE() doesn&amp;#39;t ensure ordering of the queue&amp;#39;s field
initialization before the ring-&amp;gt;queues[qid] pointer assignment. The
queue must be published with smp_store_release() so the field
initialization is guaranteed to happen before.&lt;/p&gt;
&lt;p&gt;Readers in paths where the read may happen concurrently with the store
need to use READ_ONCE() because any race involving a plain access is
undefined.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-80858</guid>
    </item>
    <item>
      <title>GHSA-4ch4-gxg4-33mh</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-4ch4-gxg4-33mh</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;fuse: publish io-uring queues with release semantics&lt;/p&gt;
&lt;p&gt;fuse_uring_create_queue() initializes a fuse_ring_queue and then
publishes the pointer into ring-&amp;gt;queues[qid] with WRITE_ONCE() under the
fch-&amp;gt;lock. There are several readers that may concurrently be fetching
that pointer locklessly and then deferencing it.&lt;/p&gt;
&lt;p&gt;WRITE_ONCE() doesn&amp;#39;t ensure ordering of the queue&amp;#39;s field
initialization before the ring-&amp;gt;queues[qid] pointer assignment. The
queue must be published with smp_store_release() so the field
initialization is guaranteed to happen before.&lt;/p&gt;
&lt;p&gt;Readers in paths where the read may happen concurrently with the store
need to use READ_ONCE() because any race involving a plain access is
undefined.&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;fuse: publish io-uring queues with release semantics&lt;/p&gt;
&lt;p&gt;fuse_uring_create_queue() initializes a fuse_ring_queue and then
publishes the pointer into ring-&amp;gt;queues[qid] with WRITE_ONCE() under the
fch-&amp;gt;lock. There are several readers that may concurrently be fetching
that pointer locklessly and then deferencing it.&lt;/p&gt;
&lt;p&gt;WRITE_ONCE() doesn&amp;#39;t ensure ordering of the queue&amp;#39;s field
initialization before the ring-&amp;gt;queues[qid] pointer assignment. The
queue must be published with smp_store_release() so the field
initialization is guaranteed to happen before.&lt;/p&gt;
&lt;p&gt;Readers in paths where the read may happen concurrently with the store
need to use READ_ONCE() because any race involving a plain access is
undefined.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-4ch4-gxg4-33mh</guid>
    </item>
    <item>
      <title>openSUSE-SU-2026:11773-1 — kernel-devel-7.2.5-1.1 on GA media</title>
      <link>https://cve.radiocsirt.org/vuln/opensuse-su-2026:11773-1</link>
      <description>&lt;p&gt;kernel-devel-7.2.5-1.1 on GA media&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;kernel-devel-7.2.5-1.1 on GA media&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/opensuse-su-2026:11773-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-80858</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-80858</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 120 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: fuse: publish io-uring queues with release semantics fuse_uring_create_queue() initializes a fuse_ring_queue and then publishes the pointer into ring-&amp;gt;queues[qid] with WRITE_ONCE() under the fch-&amp;gt;lock. There are several readers that may concurrently be fetching that pointer locklessly and then deferencing it. WRITE_ONCE() doesn&amp;#39;t ensure ordering of the queue&amp;#39;s field initialization before the ring-&amp;gt;queues[qid] pointer assignment. The queue must be published with smp_store_release() so the field initialization is guaranteed to happen before. Readers in paths where the read may happen concurrently with the store need to use READ_ONCE() because any race involving a plain access is undefined.&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 120 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: fuse: publish io-uring queues with release semantics fuse_uring_create_queue() initializes a fuse_ring_queue and then publishes the pointer into ring-&amp;gt;queues[qid] with WRITE_ONCE() under the fch-&amp;gt;lock. There are several readers that may concurrently be fetching that pointer locklessly and then deferencing it. WRITE_ONCE() doesn&amp;#39;t ensure ordering of the queue&amp;#39;s field initialization before the ring-&amp;gt;queues[qid] pointer assignment. The queue must be published with smp_store_release() so the field initialization is guaranteed to happen before. Readers in paths where the read may happen concurrently with the store need to use READ_ONCE() because any race involving a plain access is undefined.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-80858</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-3211 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-3211</link>
      <description>&lt;p&gt;Ein entfernter, anonymer Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um Speicherfehler und Kernel-Abstürze beziehungsweise Denial-of-Service-Zustände auszulösen, Speicher außerhalb vorgesehener Grenzen auszulesen sowie in einzelnen Fällen weitere Sicherheitsauswirkungen zu verursachen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein entfernter, anonymer Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um Speicherfehler und Kernel-Abstürze beziehungsweise Denial-of-Service-Zustände auszulösen, Speicher außerhalb vorgesehener Grenzen auszulesen sowie in einzelnen Fällen weitere Sicherheitsauswirkungen zu verursachen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2026-3211</guid>
    </item>
  </channel>
</rss>
