<?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>Wed, 30 Sep 2026 03:39:26 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-90140 — cuse: wait for pending RCU callbacks on module exit</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-90140</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;cuse: wait for pending RCU callbacks on module exit&lt;/p&gt;
&lt;p&gt;Since commit 053fc4f755ad (&amp;#34;fuse: fix UAF in rcu pathwalks&amp;#34;),
fuse_conn_put() frees the fuse_conn through call_rcu() rather than
synchronously.  For cuse, fc-&amp;gt;release is cuse_fc_release(), which
lives in the cuse module.  If the module is removed before the RCU
grace period ends, the callback jumps into freed module memory:&lt;/p&gt;
&lt;p&gt;userspace / module unload      |        RCU softirq
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 close(/dev/cuse)                    |
  cuse_channel_release()             |
   fuse_dev_release()                |
    fuse_conn_put(fch-&amp;gt;conn)         |
     call_rcu(delayed_release) ------+---&amp;gt; callback queued
                                     |
 rmmod cuse                          |
  cuse_exit()                        |
   cuse_channel_destroy()            |
   ...                               |
   return                            |
                                     |
 &amp;lt;module text freed&amp;gt;                 |
                                     |  rcu_do_batch()
                                     |   delayed_release()
                                     |    fc-&amp;gt;release()
                                     |     -&amp;gt; cuse_fc_release()
                                     |        ^^^ freed text!&lt;/p&gt;
&lt;p&gt;The freed module text is unmapped by vfree(), so the jump into the
stale callback triggers a pag…&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;cuse: wait for pending RCU callbacks on module exit&lt;/p&gt;
&lt;p&gt;Since commit 053fc4f755ad (&amp;#34;fuse: fix UAF in rcu pathwalks&amp;#34;),
fuse_conn_put() frees the fuse_conn through call_rcu() rather than
synchronously.  For cuse, fc-&amp;gt;release is cuse_fc_release(), which
lives in the cuse module.  If the module is removed before the RCU
grace period ends, the callback jumps into freed module memory:&lt;/p&gt;
&lt;p&gt;userspace / module unload      |        RCU softirq
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 close(/dev/cuse)                    |
  cuse_channel_release()             |
   fuse_dev_release()                |
    fuse_conn_put(fch-&amp;gt;conn)         |
     call_rcu(delayed_release) ------+---&amp;gt; callback queued
                                     |
 rmmod cuse                          |
  cuse_exit()                        |
   cuse_channel_destroy()            |
   ...                               |
   return                            |
                                     |
 &amp;lt;module text freed&amp;gt;                 |
                                     |  rcu_do_batch()
                                     |   delayed_release()
                                     |    fc-&amp;gt;release()
                                     |     -&amp;gt; cuse_fc_release()
                                     |        ^^^ freed text!&lt;/p&gt;
&lt;p&gt;The freed module text is unmapped by vfree(), so the jump into the
stale callback triggers a pag…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-90140</guid>
    </item>
  </channel>
</rss>
