CVE-2021-47192

scsi: core: sysfs: Fix hang when device state is set via sysfs

State
Published
Severity
5.3 Medium
Published
Apr 10, 2024
Updated
May 23, 2026
Reserved
Mar 25, 2024

Read the record on cve.org

Description

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.

Scores

CVSSScoreVectorSource
3.15.3 MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:NCISA-ADP

Weaknesses

The record names no weakness.

Affected Products

ProductVersions
LinuxLinux
  • 69aa1a1a569f5c6d554b59352130ef363342ed4c to before edd783162bf2385b43de6764f2d4c6e9f4f6be27Affected
  • 711459514e297d748f15ba1f5292a3276c3d1dd0 to before a792e0128d232251edb5fdf42fb0f9fbb0b44a73Affected
  • f0f82e2476f6adb9c7a0135cfab8091456990c99 to before bcc0e3175a976b7fa9a353960808adb0bb49ead8Affected
  • f0f82e2476f6adb9c7a0135cfab8091456990c99 to before 4edd8cd4e86dd3047e5294bbefcc0a08f66a430fAffected
  • c6751ce1a2a415a78e4f5b621628da03196b804cAffected
  • 5.4.143 to before 5.4.162Affected
  • 5.10.61 to before 5.10.82Affected
  • 5.13.13 to before 5.14Affected
LinuxLinux
  • 5.14Affected
  • before 5.14Not affected
  • 5.4.162 through 5.4.*Not affected
  • 5.10.82 through 5.10.*Not affected
  • 5.15.5 through 5.15.*Not affected
  • 5.16 and laterNot affected

References

Every record here comes from the CVE Program’s CVE List. © 1999–2026 The MITRE Corporation. CVE is a registered trademark of The MITRE Corporation. The records are reproduced under the CVE Program terms of use.