<?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://vulnerability.circl.lu</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>Tue, 29 Sep 2026 23:50:03 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-80858 — fuse: publish io-uring queues with release semantics</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-80858</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&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;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&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://vulnerability.circl.lu/vuln/cve-2026-80858</guid>
    </item>
  </channel>
</rss>
