--- id: CVE-2024-26935 title: |- 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… summary: |- 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… severity: medium cvss: 5.5 cvssVector: 'CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H' vendor: linux product: linux_kernel affected: - 'linux_kernel >= 5.4.238, < 5.4.274' - 'linux_kernel >= 5.10.176, < 5.10.215' - 'linux_kernel >= 5.15.104, < 5.15.154' - 'linux_kernel >= 6.1.21, < 6.1.84' - 'linux_kernel >= 6.2.8, < 6.3' - 'linux_kernel >= 6.3.1, < 6.6.24' - 'linux_kernel >= 6.7, < 6.7.12' - 'linux_kernel >= 6.8, < 6.8.3' - linux_kernel = 6.3 - linux_kernel = 6.9 - debian_linux = 10.0 patched: - linux_kernel 6.8.3 published: '2024-05-01' updated: '2026-10-15' sourceUpdated: '2026-10-15T01:17:32.727' source: NVD sourceUrl: 'https://nvd.nist.gov/vuln/detail/CVE-2024-26935' references: - url: 'https://git.kernel.org/stable/c/0053f15d50d50c9312d8ab9c11e2e405812dfcac' label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67 - url: 'https://git.kernel.org/stable/c/3678cf67ff7136db1dd3bf63c361650db5d92889' label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67 - url: 'https://git.kernel.org/stable/c/5c2386ba80e779a92ec3bb64ccadbedd88f779b1' label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67 - url: 'https://git.kernel.org/stable/c/cea234bb214b17d004dfdccce4491e6ff57c96ee' label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67 - url: 'https://git.kernel.org/stable/c/d4c34782b6d7b1e68d18d9549451b19433bd4c6c' label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67 - url: 'https://git.kernel.org/stable/c/e293c773c13b830cdc251f155df2254981abc320' label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67 - url: 'https://git.kernel.org/stable/c/f23a4d6e07570826fe95023ca1aa96a011fa9f84' label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67 - url: 'https://git.kernel.org/stable/c/f4ff08fab66eb5c0b97e1a24edac052fb40bf5d7' label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67 - url: 'https://git.kernel.org/stable/c/0053f15d50d50c9312d8ab9c11e2e405812dfcac' label: af854a3a-2127-422b-91ae-364da2661108 - url: 'https://git.kernel.org/stable/c/3678cf67ff7136db1dd3bf63c361650db5d92889' label: af854a3a-2127-422b-91ae-364da2661108 - url: 'https://git.kernel.org/stable/c/5c2386ba80e779a92ec3bb64ccadbedd88f779b1' label: af854a3a-2127-422b-91ae-364da2661108 - url: 'https://git.kernel.org/stable/c/cea234bb214b17d004dfdccce4491e6ff57c96ee' label: af854a3a-2127-422b-91ae-364da2661108 - url: 'https://git.kernel.org/stable/c/d4c34782b6d7b1e68d18d9549451b19433bd4c6c' label: af854a3a-2127-422b-91ae-364da2661108 - url: 'https://git.kernel.org/stable/c/e293c773c13b830cdc251f155df2254981abc320' label: af854a3a-2127-422b-91ae-364da2661108 - url: 'https://git.kernel.org/stable/c/f23a4d6e07570826fe95023ca1aa96a011fa9f84' label: af854a3a-2127-422b-91ae-364da2661108 - url: 'https://git.kernel.org/stable/c/f4ff08fab66eb5c0b97e1a24edac052fb40bf5d7' label: af854a3a-2127-422b-91ae-364da2661108 - url: 'https://lists.debian.org/debian-lts-announce/2024/06/msg00017.html' label: af854a3a-2127-422b-91ae-364da2661108 - url: 'https://cert-portal.siemens.com/productcert/html/ssa-265688.html' label: 0b142b55-0307-4c5a-b3c9-f314f3fb7c5e tags: - nvd - cve.org epss: 0.00242 epssPercentile: 0.1529 ingestedAt: '2026-10-15T03:30:12.662Z' ssvc: exploitation: none automatable: 'no' technicalImpact: partial timestamp: '2024-06-21T14:41:52.902192Z' --- ## Overview 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. ## Affected - `linux_kernel >= 5.4.238, < 5.4.274` - `linux_kernel >= 5.10.176, < 5.10.215` - `linux_kernel >= 5.15.104, < 5.15.154` - `linux_kernel >= 6.1.21, < 6.1.84` - `linux_kernel >= 6.2.8, < 6.3` - `linux_kernel >= 6.3.1, < 6.6.24` - `linux_kernel >= 6.7, < 6.7.12` - `linux_kernel >= 6.8, < 6.8.3` - `linux_kernel = 6.3` - `linux_kernel = 6.9` - `debian_linux = 10.0` ## Remediation Upgrade past the affected range: - `linux_kernel 6.8.3`