CVE-2021-47192: In the Linux kernel, the following vulnerability has been resolved: scsi: core: sysfs: Fix hang when device state is set via sysfs This fixes a regression…

PriorityP425medium5.3CVSS 3.1

AVNACLPRNUINSUCLINAN

EPSS

0.61%

45.9th percentile

In the Linux kernel, the following vulnerability has been resolved: scsi: core: sysfs: Fix hang when device state is set via sysfs This fixes a regression added with: commit f0f82e2476f6 ("scsi: core: Fix capacity set to zero after offlinining device") The problem is that after iSCSI recovery, iscsid will call into the kernel to set the dev's state to running, and with that patch we now call scsi_rescan_device() with the state_mutex held. If the SCSI error handler thread is just starting to test the device in scsi_send_eh_cmnd() then it's going to try to grab the state_mutex. We are then stuck, because when scsi_rescan_device() tries to send its I/O scsi_queue_rq() calls -> scsi_host_queue_ready() -> scsi_host_in_recovery() which will return true (the host state is still in recovery) and I/O will just be requeued. scsi_send_eh_cmnd() will then never be able to grab the state_mutex to finish error handling. To prevent the deadlock move the rescan-related code to after we drop the state_mutex. This also adds a check for if we are already in the running state. This prevents extra scans and helps the iscsid case where if the transport class has already onlined the device during its recovery process then we don't need userspace to do it again plus possibly block that daemon.

Affected

18 ranges

Vendor	Product	Version range	Fixed in
debian	linux	< linux 5.15.5-1 (bookworm)	linux 5.15.5-1 (bookworm)
linux	linux	—	—
linux	linux	—	—
linux	linux	>= 5.10.61 < 5.10.82	5.10.82
linux	linux	>= 5.13.13 < 5.14	5.14
linux	linux	>= 5.4.143 < 5.4.162	5.4.162
linux	linux	>= 69aa1a1a569f5c6d554b59352130ef363342ed4c < edd783162bf2385b43de6764f2d4c6e9f4f6be27	edd783162bf2385b43de6764f2d4c6e9f4f6be27
linux	linux	>= 711459514e297d748f15ba1f5292a3276c3d1dd0 < a792e0128d232251edb5fdf42fb0f9fbb0b44a73	a792e0128d232251edb5fdf42fb0f9fbb0b44a73
linux	linux	>= f0f82e2476f6adb9c7a0135cfab8091456990c99 < bcc0e3175a976b7fa9a353960808adb0bb49ead8	bcc0e3175a976b7fa9a353960808adb0bb49ead8
linux	linux	>= f0f82e2476f6adb9c7a0135cfab8091456990c99 < 4edd8cd4e86dd3047e5294bbefcc0a08f66a430f	4edd8cd4e86dd3047e5294bbefcc0a08f66a430f
linux	linux_kernel	—	—
linux	linux_kernel	>= 0 < 5.10.84-1	5.10.84-1
linux	linux_kernel	>= 0 < 5.15.5-1	5.15.5-1
linux	linux_kernel	>= 0 < 5.15.5-1	5.15.5-1
linux	linux_kernel	>= 0 < 5.15.5-1	5.15.5-1
linux	linux_kernel	>= 5.10.61 < 5.10.82	5.10.82
linux	linux_kernel	>= 5.13.13 < 5.15.5	5.15.5
linux	linux_kernel	>= 5.4.143 < 5.4.162	5.4.162

CVSS provenance

nvdv3.15.3MEDIUMCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

osv5.3MEDIUM

vendor_debian5.3MEDIUM

vendor_redhat5.3MEDIUM

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.