Heimdall Security Logo

CVE-2026-97927

Vulnérabilité non évaluée dans Linux (Linux)

CVSS 0.0 · Non évaluée
EPSS 0.2%
Linux•Linux•Versions : <=6.1.*, <=6.12.*, 7.2.7, 2.6.12, <785e523b6c1931d802cab9f85912f3e6c7028af1, 6.18.53, 0, <e58db6c2dce6e453dca26c3a4953002425201880, <2.6.12, 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, <55a4c98abb9694b067c6a031d11501f06b6b523c, 5.10.271, 6.6.158, <=5.10.*, <=6.6.*, <8173e051a8acbb4ae6547be0436727944119e0b5, 6.1.189, <=6.18.*, 5.15.222, 7.3, <=7.2.*, <05360c6eb8388bb5adac3c439ffb1512de39550a, <=*, <cd21f1ff74b1c15077fa3b98e80da3b41055aae4, <=5.15.*, <a9804121d55aaa4319c1cac00b99794aa177dd6a, 6.12.111, <5cc48633fb76196b596a449ba1f4f642ad6125ce

Description

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.

Gravité et risque d'exploitation

CVE-2026-97927 obtient un score CVSS de 0.0/10, soit une gravité non évaluée. Selon le modèle EPSS, la probabilité qu'elle soit exploitée dans les 30 prochains jours est de 0.21 %, ce qui la place devant 10.6 % des CVE référencées.

Que faire ?

  • Vérifiez si Linux (versions <=6.1.*, <=6.12.*, 7.2.7, 2.6.12, <785e523b6c1931d802cab9f85912f3e6c7028af1, 6.18.53, 0, <e58db6c2dce6e453dca26c3a4953002425201880, <2.6.12, 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, <55a4c98abb9694b067c6a031d11501f06b6b523c, 5.10.271, 6.6.158, <=5.10.*, <=6.6.*, <8173e051a8acbb4ae6547be0436727944119e0b5, 6.1.189, <=6.18.*, 5.15.222, 7.3, <=7.2.*, <05360c6eb8388bb5adac3c439ffb1512de39550a, <=*, <cd21f1ff74b1c15077fa3b98e80da3b41055aae4, <=5.15.*, <a9804121d55aaa4319c1cac00b99794aa177dd6a, 6.12.111, <5cc48633fb76196b596a449ba1f4f642ad6125ce) est présent sur votre parc.
  • Appliquez le correctif ou la version corrigée indiqués dans les références de l'éditeur.
  • À défaut de correctif, limitez l'exposition (filtrage réseau, désactivation du composant).
  • Automatisez la détection : les agents CVE Heimdall (gratuits, open source) corrèlent l'inventaire de vos serveurs avec la base CVE.

Références

Rechercher une autre CVE