<?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 01:25:01 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-90139 — fuse: check for NULL root inode in fuse_fill_super_submount</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-90139</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: check for NULL root inode in fuse_fill_super_submount&lt;/p&gt;
&lt;p&gt;fuse_iget() can return NULL when its inode allocation fails, but
fuse_fill_super_submount() passed the result straight to get_fuse_inode()
and decremented fi-&amp;gt;nlookup without checking it:&lt;/p&gt;
&lt;p&gt;root = fuse_iget(sb, parent_fi-&amp;gt;nodeid, ...);
        fi = get_fuse_inode(root);
        fi-&amp;gt;nlookup--;&lt;/p&gt;
&lt;p&gt;Inside fuse_iget() the inode allocation can fail and return NULL.  The
submount root takes the iget5_locked() path, whose alloc_inode() can fail
under memory pressure (the auto-submount branch can fail the same way in
new_inode() or fuse_alloc_submount_lookup()):&lt;/p&gt;
&lt;p&gt;inode = iget5_locked(sb, nodeid, fuse_inode_eq, fuse_inode_set,
                             &amp;amp;nodeid);
        if (!inode)
                return NULL;&lt;/p&gt;
&lt;p&gt;A NULL root makes get_fuse_inode() a container_of() on NULL and the
nlookup decrement a write to a bogus address, oopsing the mount.  With
CONFIG_KASAN the following null pointer dereference is reported when the
root inode allocation of an auto-submount fails (e.g. under memory
pressure):&lt;/p&gt;
&lt;p&gt;==================================================================
BUG: KASAN: null-ptr-deref in fuse_get_tree_submount+0x656/0x8b0
Read of size 8 at addr 00000000000002b0 by task ls/942
CPU: 0 PID: 942 Comm: ls Tainted: G W 6.6 #15
Call Trace:
 &amp;lt;TASK&amp;gt;
 fuse_get_tree_submount+0x656/0x8b0
 vfs_get_tree+0x48/0x140
 fc_mount+0x13/0x50
 fuse_dentry_aut…&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: check for NULL root inode in fuse_fill_super_submount&lt;/p&gt;
&lt;p&gt;fuse_iget() can return NULL when its inode allocation fails, but
fuse_fill_super_submount() passed the result straight to get_fuse_inode()
and decremented fi-&amp;gt;nlookup without checking it:&lt;/p&gt;
&lt;p&gt;root = fuse_iget(sb, parent_fi-&amp;gt;nodeid, ...);
        fi = get_fuse_inode(root);
        fi-&amp;gt;nlookup--;&lt;/p&gt;
&lt;p&gt;Inside fuse_iget() the inode allocation can fail and return NULL.  The
submount root takes the iget5_locked() path, whose alloc_inode() can fail
under memory pressure (the auto-submount branch can fail the same way in
new_inode() or fuse_alloc_submount_lookup()):&lt;/p&gt;
&lt;p&gt;inode = iget5_locked(sb, nodeid, fuse_inode_eq, fuse_inode_set,
                             &amp;amp;nodeid);
        if (!inode)
                return NULL;&lt;/p&gt;
&lt;p&gt;A NULL root makes get_fuse_inode() a container_of() on NULL and the
nlookup decrement a write to a bogus address, oopsing the mount.  With
CONFIG_KASAN the following null pointer dereference is reported when the
root inode allocation of an auto-submount fails (e.g. under memory
pressure):&lt;/p&gt;
&lt;p&gt;==================================================================
BUG: KASAN: null-ptr-deref in fuse_get_tree_submount+0x656/0x8b0
Read of size 8 at addr 00000000000002b0 by task ls/942
CPU: 0 PID: 942 Comm: ls Tainted: G W 6.6 #15
Call Trace:
 &amp;lt;TASK&amp;gt;
 fuse_get_tree_submount+0x656/0x8b0
 vfs_get_tree+0x48/0x140
 fc_mount+0x13/0x50
 fuse_dentry_aut…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-90139</guid>
    </item>
  </channel>
</rss>
