CVE-2026-23292

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

CVSS 0.0 · Non évaluée
EPSS 0.1%
Linux•Linux•Versions : <=6.1.*, <=6.12.*, 0, 49824b5c875087a52672b0c8e8ecbefe6f773532, 7.0, <4.10, 09e21253d17f53bdb5aac0e0dbd057a29fcbe8d1, <142eacb50fb903a4c10dee7e67b6e79ebb36a582, 4.19.84, 6.18.17, 4.9.201, <14d4ac19d1895397532eec407433c5d74d9da53b, 4.14.154, <4.20, <e8ef82cb6443d5f3260b1b830e17f03dda4229ea, <=6.6.*, <3161ef61f121d4573cad5b57c92188dcd9b284b3, <=6.19.*, <4fcfa424a581d823cb1a9676e3eefe6ca17e453a, 5.3, <=6.18.*, <5.3, 6.19.7, 6.1.167, <=*, b0841eefd9693827afb9888235e26ddd098f9cef, <9a5641024fbfd9b24fe65984ad85fea10a3ae438, 6.12.77, <4.15, 6.6.130, 0dfc45be875a378c2a3a4d6ed8e668ec8eb75073

Description

In the Linux kernel, the following vulnerability has been resolved: scsi: target: Fix recursive locking in __configfs_open_file() In flush_write_buffer, &p->frag_sem is acquired and then the loaded store function is called, which, here, is target_core_item_dbroot_store(). This function called filp_open(), following which these functions were called (in reverse order), according to the call trace: down_read __configfs_open_file do_dentry_open vfs_open do_open path_openat do_filp_open file_open_name filp_open target_core_item_dbroot_store flush_write_buffer configfs_write_iter target_core_item_dbroot_store() tries to validate the new file path by trying to open the file path provided to it; however, in this case, the bug report shows: db_root: not a directory: /sys/kernel/config/target/dbroot indicating that the same configfs file was tried to be opened, on which it is currently working on. Thus, it is trying to acquire frag_sem semaphore of the same file of which it already holds the semaphore obtained in flush_write_buffer(), leading to acquiring the semaphore in a nested manner and a possibility of recursive locking. Fix this by modifying target_core_item_dbroot_store() to use kern_path() instead of filp_open() to avoid opening the file using filesystem-specific function __configfs_open_file(), and further modifying it to make this fix compatible.

Gravité et risque d'exploitation

CVE-2026-23292 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.12 %, ce qui la place devant 1.8 % des CVE référencées.

Que faire ?

  • Vérifiez si Linux (versions <=6.1.*, <=6.12.*, 0, 49824b5c875087a52672b0c8e8ecbefe6f773532, 7.0, <4.10, 09e21253d17f53bdb5aac0e0dbd057a29fcbe8d1, <142eacb50fb903a4c10dee7e67b6e79ebb36a582, 4.19.84, 6.18.17, 4.9.201, <14d4ac19d1895397532eec407433c5d74d9da53b, 4.14.154, <4.20, <e8ef82cb6443d5f3260b1b830e17f03dda4229ea, <=6.6.*, <3161ef61f121d4573cad5b57c92188dcd9b284b3, <=6.19.*, <4fcfa424a581d823cb1a9676e3eefe6ca17e453a, 5.3, <=6.18.*, <5.3, 6.19.7, 6.1.167, <=*, b0841eefd9693827afb9888235e26ddd098f9cef, <9a5641024fbfd9b24fe65984ad85fea10a3ae438, 6.12.77, <4.15, 6.6.130, 0dfc45be875a378c2a3a4d6ed8e668ec8eb75073) 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