cbcvebase.
CVE-2024-26935
published 2024-05-01

CVE-2024-26935: In the Linux kernel, the following vulnerability has been resolved: scsi: core: Fix unremoved procfs host directory regression Commit fc663711b944 ("scsi…

PriorityP421medium5.5CVSS 3.1
AVLACLPRLUINSUCNINAH
EPSS
0.24%
15.5th percentile
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,remo

Affected

38 ranges· showing 25
VendorProductVersion rangeFixed in
debiandebian_linux
debianlinux< linux 6.1.85-1 (bookworm)linux 6.1.85-1 (bookworm)
linuxlinux
linuxlinux
linuxlinux>= 2a764d55e938743efa7c2cba7305633bcf227f09 < cea234bb214b17d004dfdccce4491e6ff57c96eecea234bb214b17d004dfdccce4491e6ff57c96ee
linuxlinux>= 5.10.176 < 5.10.2155.10.215
linuxlinux>= 5.15.104 < 5.15.1545.15.154
linuxlinux>= 5.4.238 < 5.4.2745.4.274
linuxlinux>= 6.1.21 < 6.1.846.1.84
linuxlinux>= 6.2.8 < 6.36.3
linuxlinux>= 68c665bb185037e7eb66fb792c61da9d7151e99c < 5c2386ba80e779a92ec3bb64ccadbedd88f779b15c2386ba80e779a92ec3bb64ccadbedd88f779b1
linuxlinux>= 7e0ae8667fcdd99d1756922e1140cac75f5fa279 < 3678cf67ff7136db1dd3bf63c361650db5d928893678cf67ff7136db1dd3bf63c361650db5d92889
linuxlinux>= 88c3d3bb6469cea929ac68fd326bdcbefcdfdd83 < 0053f15d50d50c9312d8ab9c11e2e405812dfcac0053f15d50d50c9312d8ab9c11e2e405812dfcac
linuxlinux>= be03df3d4bfe7e8866d4aa43d62e648ffe884f5f < d4c34782b6d7b1e68d18d9549451b19433bd4c6cd4c34782b6d7b1e68d18d9549451b19433bd4c6c
linuxlinux>= be03df3d4bfe7e8866d4aa43d62e648ffe884f5f < e293c773c13b830cdc251f155df2254981abc320e293c773c13b830cdc251f155df2254981abc320
linuxlinux>= be03df3d4bfe7e8866d4aa43d62e648ffe884f5f < f4ff08fab66eb5c0b97e1a24edac052fb40bf5d7f4ff08fab66eb5c0b97e1a24edac052fb40bf5d7
linuxlinux>= be03df3d4bfe7e8866d4aa43d62e648ffe884f5f < f23a4d6e07570826fe95023ca1aa96a011fa9f84f23a4d6e07570826fe95023ca1aa96a011fa9f84
linuxlinux_kernel
linuxlinux_kernel
linuxlinux_kernel>= 0 < 5.10.216-15.10.216-1
linuxlinux_kernel>= 0 < 6.1.85-16.1.85-1
linuxlinux_kernel>= 0 < 6.7.12-16.7.12-1
linuxlinux_kernel>= 0 < 6.7.12-16.7.12-1
linuxlinux_kernel>= 0 < 5.4.0-189.2095.4.0-189.209
linuxlinux_kernel>= 0 < 5.15.0-116.1265.15.0-116.126

CVSS provenance

nvdv3.15.5MEDIUMCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
osv7.0HIGH
vendor_ubuntu7.0HIGH
vendor_debian5.5MEDIUM
vendor_msrc5.5LOW
vendor_redhat5.5MEDIUM
Stop checking back — get the weekly exploitation signal.

Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.