<?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 20:16:33 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-97927 — ufs: create the root dentry after loading cylinder metadata</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-97927</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;ufs: create the root dentry after loading cylinder metadata&lt;/p&gt;
&lt;p&gt;ufs_fill_super() installed sb-&amp;gt;s_root before it loaded the cylinder
group structures for a writable mount:&lt;/p&gt;
&lt;p&gt;sb-&amp;gt;s_root = d_make_root(inode);
	...
	if (!sb_rdonly(sb))
		if (!ufs_read_cylinder_structures(sb))
			goto failed;&lt;/p&gt;
&lt;p&gt;When ufs_read_cylinder_structures() failed, the error path freed the
in-core superblock information and set sb-&amp;gt;s_fs_info to NULL while
sb-&amp;gt;s_root stayed installed. get_tree_bdev() then reached
deactivate_locked_super(), and because s_root was present,
generic_shutdown_super() called sync_filesystem() and the put_super
operation. Both dereference UFS_SB(sb), which is now NULL, so a mount
that fails only while reading the cylinder groups oopses during
teardown. A crafted image whose first cylinder group cannot be read
reaches this path.&lt;/p&gt;
&lt;p&gt;Load the cylinder group metadata first and create the root dentry last,
so the superblock is published to the VFS only once it is fully set up.
ufs_setup_cstotal() and ufs_read_cylinder_structures() take only the
super_block and do not use the root inode, so the reordering is safe.&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;ufs: create the root dentry after loading cylinder metadata&lt;/p&gt;
&lt;p&gt;ufs_fill_super() installed sb-&amp;gt;s_root before it loaded the cylinder
group structures for a writable mount:&lt;/p&gt;
&lt;p&gt;sb-&amp;gt;s_root = d_make_root(inode);
	...
	if (!sb_rdonly(sb))
		if (!ufs_read_cylinder_structures(sb))
			goto failed;&lt;/p&gt;
&lt;p&gt;When ufs_read_cylinder_structures() failed, the error path freed the
in-core superblock information and set sb-&amp;gt;s_fs_info to NULL while
sb-&amp;gt;s_root stayed installed. get_tree_bdev() then reached
deactivate_locked_super(), and because s_root was present,
generic_shutdown_super() called sync_filesystem() and the put_super
operation. Both dereference UFS_SB(sb), which is now NULL, so a mount
that fails only while reading the cylinder groups oopses during
teardown. A crafted image whose first cylinder group cannot be read
reaches this path.&lt;/p&gt;
&lt;p&gt;Load the cylinder group metadata first and create the root dentry last,
so the superblock is published to the VFS only once it is fully set up.
ufs_setup_cstotal() and ufs_read_cylinder_structures() take only the
super_block and do not use the root inode, so the reordering is safe.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-97927</guid>
    </item>
  </channel>
</rss>
