CVE-2021-47192scsi: core: sysfs: Fix hang when device state is set via sysfs
- 5.3MediumCVSS base score
- 0.61%Exploitation in 30 daysEPSS · top 50% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
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.
Timeline
ID reserved
By Linux
- 16 days later
· 16 days later
Published
- 2 years later
· 2 years later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| CISA-ADPADP (enrichment) | 3.1 | Medium5.3 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N |
| NVDNVD · Analyzed | 3.1 | Medium5.3 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N |
- EPSS (exploitation in 30 days)
- 0.61% · top 50% of all CVEs (12 Nov 2026)
- CISA SSVC
- Exploitation: none · Automatable: no · Technical impact: partial
The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.3.
Affected products
- affected 69aa1a1a569f5c6d554b59352130ef363342ed4c – < edd783162bf2385b43de6764f2d4c6e9f4f6be27
- affected 711459514e297d748f15ba1f5292a3276c3d1dd0 – < a792e0128d232251edb5fdf42fb0f9fbb0b44a73
- affected f0f82e2476f6adb9c7a0135cfab8091456990c99 – < bcc0e3175a976b7fa9a353960808adb0bb49ead8
- affected f0f82e2476f6adb9c7a0135cfab8091456990c99 – < 4edd8cd4e86dd3047e5294bbefcc0a08f66a430f
- affected c6751ce1a2a415a78e4f5b621628da03196b804c
- affected 5.4.143 – < 5.4.162
- affected 5.10.61 – < 5.10.82
- affected 5.13.13 – < 5.14
- affected 5.14
- unaffected < 5.14
- unaffected 5.4.162 – ≤ 5.4.*
- unaffected 5.10.82 – ≤ 5.10.*
- unaffected 5.15.5 – ≤ 5.15.*
- unaffected 5.16 – ≤ *
References
References4
- https://git.kernel.org/stable/c/edd783162bf2385b43de6764f2d4c6e9f4f6be27 (opens in a new tab)x_transferred
- https://git.kernel.org/stable/c/a792e0128d232251edb5fdf42fb0f9fbb0b44a73 (opens in a new tab)x_transferred
- https://git.kernel.org/stable/c/bcc0e3175a976b7fa9a353960808adb0bb49ead8 (opens in a new tab)x_transferred
- https://git.kernel.org/stable/c/4edd8cd4e86dd3047e5294bbefcc0a08f66a430f (opens in a new tab)x_transferred
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2021-33840 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2021-47192)Record last updated .