CVE-2026-97927

ufs: create the root dentry after loading cylinder metadata

CVE-2026-97927 is fixed in 2 products on 1 platform, first by DEBIAN-CVE-2026-97927, released September 29, 2026. It is not reported as exploited. Patch Radar priority: Routine.

Routine
CVSS
5.5
Moderate
Exploitation
None reported
No vendor assessment
CISA KEV
Not listed
Not in the Known Exploited Vulnerabilities catalog
EPSS
0.0021
11th percentile

In the Linux kernel, the following vulnerability has been resolved: ufs: create the root dentry after loading cylinder metadata ufs_fill_super() installed sb->s_root before it loaded the cylinder group structures for a writable mount: sb->s_root = d_make_root(inode); ... if (!sb_rdonly(sb)) if (!ufs_read_cylinder_structures(sb)) goto failed; When ufs_read_cylinder_structures() failed, the error path freed the in-core superblock information and set sb->s_fs_info to NULL while sb->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. 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.

Where it's fixed

ProductFixed inFixReleased
Linux
linux · Debian 12.15 (bookworm) 6.1.190-1 DEBIAN-CVE-2026-97927 Sep 29, 2026
linux · Debian 13.5 (trixie) 6.12.111-1 DEBIAN-CVE-2026-97927 Sep 29, 2026
linux · Debian 14 7.2.7-1 DEBIAN-CVE-2026-97927 Sep 29, 2026
linux-6.12 · Debian 12.15 (bookworm) 6.12.111-1~deb12u1 DEBIAN-CVE-2026-97927 Sep 29, 2026

Patch Radar data is free to use with attribution. Terms and how to credit it.

Product names, logos and trademarks shown on Patch Radar belong to their respective owners. They are used only to identify the software each security fix applies to and to help readers find their platform. Their use does not imply any affiliation with, or endorsement by, those owners, and Patchblox is not affiliated with any of them.