<?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 01:53:42 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2026-90140</title>
      <link>https://vulnerability.circl.lu/vuln/bell-cve-2026-90140</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://vulnerability.circl.lu/vuln/bell-cve-2026-90140</guid>
    </item>
    <item>
      <title>fkie_cve-2026-90140</title>
      <link>https://vulnerability.circl.lu/vuln/fkie_cve-2026-90140</link>
      <description>&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;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/fkie_cve-2026-90140</guid>
    </item>
    <item>
      <title>GHSA-h4xp-2gp9-vpwg</title>
      <link>https://vulnerability.circl.lu/vuln/ghsa-h4xp-2gp9-vpwg</link>
      <description>&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;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/ghsa-h4xp-2gp9-vpwg</guid>
    </item>
    <item>
      <title>msrc_CVE-2026-90140 — cuse: wait for pending RCU callbacks on module exit</title>
      <link>https://vulnerability.circl.lu/vuln/msrc_cve-2026-90140</link>
      <description>msrc_CVE-2026-90140</description>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/msrc_cve-2026-90140</guid>
    </item>
    <item>
      <title>openSUSE-SU-2026:11880-1 — kernel-devel-7.2.7-1.1 on GA media</title>
      <link>https://vulnerability.circl.lu/vuln/opensuse-su-2026:11880-1</link>
      <description>&lt;p&gt;kernel-devel-7.2.7-1.1 on GA media&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;kernel-devel-7.2.7-1.1 on GA media&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/opensuse-su-2026:11880-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-90140</title>
      <link>https://vulnerability.circl.lu/vuln/ubuntu-cve-2026-90140</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 189 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: cuse: wait for pending RCU callbacks on module exit 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:       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! The freed module text is unmapped by vfree(), so the jump into the stale callback triggers a page-fa…&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 189 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: cuse: wait for pending RCU callbacks on module exit 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:       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! The freed module text is unmapped by vfree(), so the jump into the stale callback triggers a page-fa…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ubuntu-cve-2026-90140</guid>
    </item>
  </channel>
</rss>
