SCSI recovery hang via state_mutex deadlock
Published Apr 10, 2024 · Updated May 23, 2026
Improper locking in affected Linux kernel releases allows local users to hang SCSI recovery by setting device state through sysfs. The SCSI state-change path calls scsi_rescan_device() while holding state_mutex, while the error handler needs the same mutex and queued I/O cannot complete during host recovery. Reaching the deadlock requires privileged local sysfs access, an iSCSI recovery, and a race with SCSI error handling; the resulting impact is a storage-recovery hang.
Summary
What happened
Improper locking in affected Linux kernel releases allows local users to hang SCSI recovery by setting device state through sysfs. The SCSI state-change path calls scsi_rescan_device() while holding state_mutex, while the error handler needs the same mutex and queued I/O cannot complete during host recovery. Reaching the deadlock requires privileged local sysfs access, an iSCSI recovery, and a race with SCSI error handling; the resulting impact is a storage-recovery hang.
The record
- CVE
- CVE-2021-47192
- Published
- Apr 10, 2024
- Updated
- May 23, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-667, T1499.004
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Apr 10, 2024CVE publishedPublication date reported by the CVE source.
- May 23, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=5.10.61 <5.10.82
- Affected versionversion=5.13.13 <5.14
- Affected versionversion=5.14
- Affected versionversion=5.4.143 <5.4.162
- Affected versionversion=69aa1a1a569f5c6d554b59352130ef363342ed4c <edd783162bf2385b43de6764f2d4c6e9f4f6be27
- Affected versionversion=711459514e297d748f15ba1f5292a3276c3d1dd0 <a792e0128d232251edb5fdf42fb0f9fbb0b44a73
- Affected versionversion=c6751ce1a2a415a78e4f5b621628da03196b804c
- Affected versionversion=f0f82e2476f6adb9c7a0135cfab8091456990c99 <4edd8cd4e86dd3047e5294bbefcc0a08f66a430f
- Affected versionversion=f0f82e2476f6adb9c7a0135cfab8091456990c99 <bcc0e3175a976b7fa9a353960808adb0bb49ead8
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo