CVE-2026-97927: ufs: create the root dentry after loading cylinder metadata

Published Sep 25, 2026
·
Updated

In the Linux kernel, the following vulnerability has been resolved:

ufs: create the root dentry after loading cylinder metadata

ufsfillsuper() installed sb->sroot before it loaded the cylinder group structures for a writable mount:

sb->sroot = dmakeroot(inode); ... if (!sbrdonly(sb)) if (!ufsreadcylinderstructures(sb)) goto failed;

When ufsreadcylinderstructures() failed, the error path freed the in-core superblock information and set sb->sfsinfo to NULL while sb->sroot stayed installed. gettreebdev() then reached deactivatelockedsuper(), and because sroot was present, genericshutdownsuper() called syncfilesystem() and the putsuper operation. Both dereference UFSSB(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. ufssetupcstotal() and ufsreadcylinderstructures() take only the superblock and do not use the root inode, so the reordering is safe.

Affected Software

1 affected component
Linux Linux kernel

Event History

Sep 25, 2026
CVE Published
via MITRE·10:22 AM
Data Sourced
via MITRE·10:22 AM
Description
Data Sourced
via NVD·11:17 AM
Description

Frequently Asked Questions

1

Who is exposed to this failure path?

Systems that attempt a writable mount of a UFS filesystem are exposed if the cylinder group metadata cannot be read. A crafted UFS image with an unreadable first cylinder group can trigger it.

2

What does an attacker need to trigger the issue?

They need to cause the system to mount a crafted UFS image such that reading the first cylinder group fails. The described outcome is a kernel oops during mount teardown.

3

Are read-only UFS mounts affected?

The vulnerable cylinder-structure loading path is performed only when the filesystem is not mounted read-only. The described failure therefore applies to writable mounts.

4

How can administrators identify an affected event?

An affected event occurs when a writable UFS mount fails while reading cylinder group structures, followed by teardown through generic_shutdown_super(), sync_filesystem(), and the UFS put_super operation dereferencing a NULL UFS superblock pointer.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203