Heimdall Security Logo

CVE-2024-26935

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

CVSS 0.0 · Non évaluée
EPSS 0.2%
Linux•Linux•Versions : <5.4.274, 6.9, <=6.1.*, 0, 5.15.104, be03df3d4bfe7e8866d4aa43d62e648ffe884f5f, 5.15.154, 2a764d55e938743efa7c2cba7305633bcf227f09, <f4ff08fab66eb5c0b97e1a24edac052fb40bf5d7, 6.8.3, <6.3, <e293c773c13b830cdc251f155df2254981abc320, <=5.10.*, <=6.6.*, 5.10.215, <5c2386ba80e779a92ec3bb64ccadbedd88f779b1, 6.3, <3678cf67ff7136db1dd3bf63c361650db5d92889, <=5.4.*, 68c665bb185037e7eb66fb792c61da9d7151e99c, <6.1.84, <5.15.154, 5.4.238, 6.1.21, <cea234bb214b17d004dfdccce4491e6ff57c96ee, 5.4.274, 88c3d3bb6469cea929ac68fd326bdcbefcdfdd83, <=6.8.*, 6.2.8, 7e0ae8667fcdd99d1756922e1140cac75f5fa279, 6.7.12, 73f030d4ef6d1ad17f824a0a2eb637ef7a9c7d51, <=*, 5.10.176, <=5.15.*, <=6.7.*, <d4c34782b6d7b1e68d18d9549451b19433bd4c6c, <f23a4d6e07570826fe95023ca1aa96a011fa9f84, <0053f15d50d50c9312d8ab9c11e2e405812dfcac, 6.1.84, <5.10.215, 6.6.24

Description

In the Linux kernel, the following vulnerability has been resolved: scsi: core: Fix unremoved procfs host directory regression Commit fc663711b944 ("scsi: core: Remove the /proc/scsi/${proc_name} directory earlier") fixed a bug related to modules loading/unloading, by adding a call to scsi_proc_hostdir_rm() on scsi_remove_host(). But that led to a potential duplicate call to the hostdir_rm() routine, since it's also called from scsi_host_dev_release(). That triggered a regression report, which was then fixed by commit be03df3d4bfe ("scsi: core: Fix a procfs host directory removal regression"). The fix just dropped the hostdir_rm() call from dev_release(). But it happens that this proc directory is created on scsi_host_alloc(), and that function "pairs" with scsi_host_dev_release(), while scsi_remove_host() pairs with scsi_add_host(). In other words, it seems the reason for removing the proc directory on dev_release() was meant to cover cases in which a SCSI host structure was allocated, but the call to scsi_add_host() didn't happen. And that pattern happens to exist in some error paths, for example. Syzkaller causes that by using USB raw gadget device, error'ing on usb-storage driver, at usb_stor_probe2(). By checking that path, we can see that the BadDevice label leads to a scsi_host_put() after a SCSI host allocation, but there's no call to scsi_add_host() in such path. That leads to messages like this in dmesg (and a leak of the SCSI host proc structure): usb-storage 4-1:87.51: USB Mass Storage device detected proc_dir_entry 'scsi/usb-storage' already registered WARNING: CPU: 1 PID: 3519 at fs/proc/generic.c:377 proc_register+0x347/0x4e0 fs/proc/generic.c:376 The proper fix seems to still call scsi_proc_hostdir_rm() on dev_release(), but guard that with the state check for SHOST_CREATED; there is even a comment in scsi_host_dev_release() detailing that: such conditional is meant for cases where the SCSI host was allocated but there was no calls to {add,remove}_host(), like the usb-storage case. This is what we propose here and with that, the error path of usb-storage does not trigger the warning anymore.

Gravité et risque d'exploitation

CVE-2024-26935 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.24 %, ce qui la place devant 14.4 % des CVE référencées.

Que faire ?

  • Vérifiez si Linux (versions <5.4.274, 6.9, <=6.1.*, 0, 5.15.104, be03df3d4bfe7e8866d4aa43d62e648ffe884f5f, 5.15.154, 2a764d55e938743efa7c2cba7305633bcf227f09, <f4ff08fab66eb5c0b97e1a24edac052fb40bf5d7, 6.8.3, <6.3, <e293c773c13b830cdc251f155df2254981abc320, <=5.10.*, <=6.6.*, 5.10.215, <5c2386ba80e779a92ec3bb64ccadbedd88f779b1, 6.3, <3678cf67ff7136db1dd3bf63c361650db5d92889, <=5.4.*, 68c665bb185037e7eb66fb792c61da9d7151e99c, <6.1.84, <5.15.154, 5.4.238, 6.1.21, <cea234bb214b17d004dfdccce4491e6ff57c96ee, 5.4.274, 88c3d3bb6469cea929ac68fd326bdcbefcdfdd83, <=6.8.*, 6.2.8, 7e0ae8667fcdd99d1756922e1140cac75f5fa279, 6.7.12, 73f030d4ef6d1ad17f824a0a2eb637ef7a9c7d51, <=*, 5.10.176, <=5.15.*, <=6.7.*, <d4c34782b6d7b1e68d18d9549451b19433bd4c6c, <f23a4d6e07570826fe95023ca1aa96a011fa9f84, <0053f15d50d50c9312d8ab9c11e2e405812dfcac, 6.1.84, <5.10.215, 6.6.24) 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