CVE-2021-47192: scsi: core: sysfs: Fix hang when device state is set via sysfs
Noroxi assessment
Priority: Monitor (action score 21/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.61% (FIRST EPSS).
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 4edd8cd4e86dd3047e5294bbefcc0a08f66a430f, 5.10.82, 5.14.
- Mentioned 2 times in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Linux Linux 4edd8cd4e86dd3047e5294bbefcc0a08f66a430f, 5.10.82, 5.14 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Apr 10, 2024
- Updated
- Jun 17, 2026
- EPSS
- 0.6% · 49th percentile
- CWE
- CWE-667
Report tools
Action score
21
Monitor
Low priority for now.
- CVSS
- 21 / 40 · 5.3 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.6%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel5.4.143 and later · before 5.4.162
- linux linux kernel5.10.61 and later · before 5.10.82
- linux linux kernel5.13.13 and later · before 5.15.5
- linux linux kernel5.16
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- c6751ce1a2a415a78e4f5b621628da03196b804c, 5.14affected
- 69aa1a1a569f5c6d554b59352130ef363342ed4c and later · before edd783162bf2385b43de6764f2d4c6e9f4f6be27affected · git
- 711459514e297d748f15ba1f5292a3276c3d1dd0 and later · before a792e0128d232251edb5fdf42fb0f9fbb0b44a73affected · git
- f0f82e2476f6adb9c7a0135cfab8091456990c99 and later · before bcc0e3175a976b7fa9a353960808adb0bb49ead8affected · git
- f0f82e2476f6adb9c7a0135cfab8091456990c99 and later · before 4edd8cd4e86dd3047e5294bbefcc0a08f66a430faffected · git
- 5.4.143 and later · before 5.4.162affected · semver
- 5.10.61 and later · before 5.10.82affected · semver
- 5.13.13 and later · before 5.14affected · semver
- before 5.14not affected · semver
- 5.4.162 and later · up to and including 5.4.*not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 5.15.5-1 | 5.15.5-1 |
| openSUSE:Leap 15.5 | dtb-aarch64 | before 5.14.21-150500.55.62.1 | 5.14.21-150500.55.62.1 |
| openSUSE:Leap 15.5 | kernel-64kb | before 5.14.21-150500.55.62.2 | 5.14.21-150500.55.62.2 |
| openSUSE:Leap 15.5 | kernel-azure | before 5.14.21-150500.33.51.1 | 5.14.21-150500.33.51.1 |
| openSUSE:Leap 15.5 | kernel-debug | before 5.14.21-150500.55.62.2 | 5.14.21-150500.55.62.2 |
| openSUSE:Leap 15.5 | kernel-default | before 5.14.21-150500.55.62.2 | 5.14.21-150500.55.62.2 |
| openSUSE:Leap 15.5 | kernel-default-base | before 5.14.21-150500.55.62.2.150500.6.27.2 | 5.14.21-150500.55.62.2.150500.6.27.2 |
| openSUSE:Leap 15.5 | kernel-docs | before 5.14.21-150500.55.62.2 | 5.14.21-150500.55.62.2 |
| openSUSE:Leap 15.5 | kernel-kvmsmall | before 5.14.21-150500.55.62.2 | 5.14.21-150500.55.62.2 |
| openSUSE:Leap 15.5 | kernel-obs-build | before 5.14.21-150500.55.62.2 | 5.14.21-150500.55.62.2 |
| openSUSE:Leap 15.5 | kernel-obs-qa | before 5.14.21-150500.55.62.1 | 5.14.21-150500.55.62.1 |
| openSUSE:Leap 15.5 | kernel-rt | before 5.14.21-150500.13.52.1 | 5.14.21-150500.13.52.1 |
| openSUSE:Leap 15.5 | kernel-rt_debug | before 5.14.21-150500.13.52.1 | 5.14.21-150500.13.52.1 |
| openSUSE:Leap 15.5 | kernel-source | before 5.14.21-150500.55.62.2 | 5.14.21-150500.55.62.2 |
| openSUSE:Leap 15.5 | kernel-source-azure | before 5.14.21-150500.33.51.1 | 5.14.21-150500.33.51.1 |
| openSUSE:Leap 15.5 | kernel-source-rt | before 5.14.21-150500.13.52.1 | 5.14.21-150500.13.52.1 |
| openSUSE:Leap 15.5 | kernel-syms | before 5.14.21-150500.55.62.1 | 5.14.21-150500.55.62.1 |
| openSUSE:Leap 15.5 | kernel-syms-azure | before 5.14.21-150500.33.51.1 | 5.14.21-150500.33.51.1 |
| openSUSE:Leap 15.5 | kernel-syms-rt | before 5.14.21-150500.13.52.1 | 5.14.21-150500.13.52.1 |
| openSUSE:Leap 15.5 | kernel-zfcpdump | before 5.14.21-150500.55.62.2 | 5.14.21-150500.55.62.2 |
| openSUSE:Leap Micro 5.3 | kernel-default | before 5.14.21-150400.24.119.1 | 5.14.21-150400.24.119.1 |
| openSUSE:Leap Micro 5.3 | kernel-default-base | before 5.14.21-150400.24.119.1.150400.24.56.1 | 5.14.21-150400.24.119.1.150400.24.56.1 |
| openSUSE:Leap Micro 5.3 | kernel-rt | before 5.14.21-150400.15.79.1 | 5.14.21-150400.15.79.1 |
| SUSE:Linux Enterprise High Performance Computing 15 SP3-LTSS | kernel-64kb | before 5.3.18-150300.59.164.1 | 5.3.18-150300.59.164.1 |
+39
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2021-47190Apr 10, 2024 · perf bpf: Avoid memory leak from perf_env__insert_btf()22Monitor
- ← EarlierCVE-2021-47191Apr 10, 2024 · scsi: scsi_debug: Fix out-of-bound read in resp_readcap16()28Monitor
- Later →CVE-2021-47193Apr 10, 2024 · scsi: pm80xx: Fix memory leak during rmmod22Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 4edd8cd4e86dd3047e5294bbefcc0a08f66a430f | Vendor (CNA) |
| Linux Linux | 5.10.82 | Vendor (CNA) |
| Linux Linux | 5.14 | Vendor (CNA) |
| Linux Linux | 5.4.162 | Vendor (CNA) |
| Linux Linux | a792e0128d232251edb5fdf42fb0f9fbb0b44a73 | Vendor (CNA) |
| Linux Linux | bcc0e3175a976b7fa9a353960808adb0bb49ead8 | Vendor (CNA) |
| Linux Linux | edd783162bf2385b43de6764f2d4c6e9f4f6be27 | Vendor (CNA) |
| debian:linux | 5.15.5-1 · Debian:12 | Package registry (OSV) |
| opensuse:dtb-aarch64 | 5.14.21-150500.55.62.1 · openSUSE:Leap 15.5 | Package registry (OSV) |
| opensuse:kernel-64kb | 5.14.21-150500.55.62.2 · openSUSE:Leap 15.5 | Package registry (OSV) |
| opensuse:kernel-azure | 5.14.21-150500.33.51.1 · openSUSE:Leap 15.5 | Package registry (OSV) |
| opensuse:kernel-debug | 5.14.21-150500.55.62.2 · openSUSE:Leap 15.5 | Package registry (OSV) |
| opensuse:kernel-default | 5.14.21-150400.24.119.1 · openSUSE:Leap Micro 5.3 | Package registry (OSV) |
| opensuse:kernel-default-base | 5.14.21-150400.24.119.1.150400.24.56.1 · openSUSE:Leap Micro 5.3 | Package registry (OSV) |
| opensuse:kernel-docs | 5.14.21-150500.55.62.2 · openSUSE:Leap 15.5 | Package registry (OSV) |
| opensuse:kernel-kvmsmall | 5.14.21-150500.55.62.2 · openSUSE:Leap 15.5 | Package registry (OSV) |
| opensuse:kernel-obs-build | 5.14.21-150500.55.62.2 · openSUSE:Leap 15.5 | Package registry (OSV) |
| opensuse:kernel-rt | 5.14.21-150400.15.79.1 · openSUSE:Leap Micro 5.3 | Package registry (OSV) |
| opensuse:kernel-source-azure | 5.14.21-150500.33.51.1 · openSUSE:Leap 15.5 | Package registry (OSV) |
| opensuse:kernel-syms-azure | 5.14.21-150500.33.51.1 · openSUSE:Leap 15.5 | Package registry (OSV) |
| suse:kernel-64kb | 5.14.21-150400.24.119.1 · SUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOS | Package registry (OSV) |
| suse:kernel-azure | 5.14.21-150500.33.51.1 · SUSE:Linux Enterprise Module for Public Cloud 15 SP5 | Package registry (OSV) |
| suse:kernel-default | 5.14.21-150400.24.119.1 · SUSE:Linux Enterprise Micro 5.3 | Package registry (OSV) |
| suse:kernel-default-base | 5.14.21-150400.24.119.1.150400.24.56.1 · SUSE:Linux Enterprise Micro 5.3 | Package registry (OSV) |
| suse:kernel-docs | 5.14.21-150400.24.119.1 · SUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOS | Package registry (OSV) |
| suse:kernel-livepatch-SLE15-SP4_Update_26 | 1-150400.9.3.1 · SUSE:Linux Enterprise Live Patching 15 SP4 | Package registry (OSV) |
| suse:kernel-obs-build | 5.14.21-150400.24.119.1 · SUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOS | Package registry (OSV) |
| suse:kernel-source | 5.14.21-150400.24.119.1 · SUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOS | Package registry (OSV) |
| suse:kernel-source-azure | 5.14.21-150500.33.51.1 · SUSE:Linux Enterprise Module for Public Cloud 15 SP5 | Package registry (OSV) |
| suse:kernel-syms | 5.14.21-150400.24.119.1 · SUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOS | Package registry (OSV) |
+2
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-24-0494 · May 16, 2024(Linux Kernel Güncellemesi)
- TR-24-0284 · Apr 15, 2024(Linux Kernel Güncellemesi)
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- low · data can be read
- Integrity
- none
- Availability
- none
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- Low
- Integrity impact
- None
- Availability impact
- None
Weakness class (CWE)
CWE-667 · Improper LockingCVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (3 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.