CVE-2022-50215 — scsi: sg: Allow waiting for commands to complete on removed device
In the Linux kernel, the following vulnerability has been resolved: scsi: sg: Allow waiting for commands to complete on removed device When a SCSI device is removed while in active use, currently sg will immediately return -ENODEV on any attempt to wait for active commands that were sent before the removal. This is problematic for commands that use SG_FLAG_DIRECT_IO since the data buffer may still be in use by the kernel when userspace frees or reuses it after getting ENODEV, leading to corrupted userspace memory (in the case of READ-type commands) or corrupted data being sent to the device (in the case of WRITE-type commands). This has been seen in practice when logging out of a iscsi_tcp session, where the iSCSI driver may still be processing commands after the device has been marked for removal. Change the policy to allow userspace to wait for active sg commands even when the device is being removed. Return -ENODEV only when there are no more responses to read.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- EPSS 0.2% (30-day exploitation probability)+2
- Technical severity (medium)+3
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
CISA SSVC assessment CISA
Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
- Documented patch — git.kernel.org (NIST National Vulnerability Database)
- Documented patch — git.kernel.org (NIST National Vulnerability Database)
- Documented patch — git.kernel.org (NIST National Vulnerability Database)
- Documented patch — git.kernel.org (NIST National Vulnerability Database)
- Documented patch — git.kernel.org (NIST National Vulnerability Database)
- Documented patch — git.kernel.org (NIST National Vulnerability Database)
- Documented patch — git.kernel.org (NIST National Vulnerability Database)
- Documented patch — git.kernel.org (NIST National Vulnerability Database)
- Documented patch — git.kernel.org (NIST National Vulnerability Database)
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Linux Linux, Linux Linux Kernel).
- Apply the fixed version or the patch documented under Remediation.
- Search available logs for exploit probes, errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Linux | Linux |
≥ c6517b7942fad663cc1cf3235cbe4207cf769332 and < f135c65085eed869d10e4e7923ce1015288618daversion 2.6.30≥ 2.6.29.2 and < 2.6.30≥ 2.6.28.10 and < 2.6.29version b21c6d2897cd455fa396f4041a0c8165784e949fversion a0fe972f78eaaf352d593f9ed9079de590ceb286≥ c6517b7942fad663cc1cf3235cbe4207cf769332 and < 3455607fd7be10b449f5135c00dc306b85dc0d21≥ c6517b7942fad663cc1cf3235cbe4207cf769332 and < 03d8241112d5e3cccce1a01274a221099f07d2e1 and 6 more≥ c6517b7942fad663cc1cf3235cbe4207cf769332 and < 35e60ec39e862159cb92923eefd5230d4a873cb9≥ c6517b7942fad663cc1cf3235cbe4207cf769332 and < 8c004b7dbb340c1e5889f5fb9e5baa6f6e5303e8≥ c6517b7942fad663cc1cf3235cbe4207cf769332 and < 408bfa1489a3cfe7150b81ab0b0df99b23dd5411≥ c6517b7942fad663cc1cf3235cbe4207cf769332 and < ed9afd967cbfe7da2dc0d5e52c62a778dfe9f16b≥ c6517b7942fad663cc1cf3235cbe4207cf769332 and < f5e61d9b4a699dd16f32d5f39eb1cf98d84c92ed≥ c6517b7942fad663cc1cf3235cbe4207cf769332 and < bbc118acf7baf9e93c5e1314d14f481301af4d0f |
Vulnerable | CVE Program (cve.org) e CISA ADP |
| Linux | Linux Kernel | < 4.9.326≥ 5.19 and < 5.19.2≥ 5.16 and < 5.18.18≥ 5.11 and < 5.15.61≥ 5.5 and < 5.10.137≥ 4.20 and < 5.4.211≥ 4.15 and < 4.19.256≥ 4.10 and < 4.14.291 | Vulnerable | NIST National Vulnerability Database |
Attack characteristics
The CVSS vector, decoded. It describes the attack, not your exposure to it.
Every base score collected
Sources score independently and may disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Scored by |
|---|---|---|---|---|---|
| 7.8 | CVSS 3.1 | High | 1.8 | 5.9 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 via NIST National Vulnerability Database |
| 7.8 | CVSS 3.1 | High | — | — | Linux via CVE Program (cve.org) e CISA ADP |
| 5.5 | CVSS 3.1 | Medium | 1.8 | 3.6 | nvd@nist.gov via NIST National Vulnerability Database |
| 5.5 | CVSS 3.1 | Medium | — | — | GitHub, Inc. via GitHub Security Advisories |
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H (score shown at the top: nvd@nist.gov) Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Local/physical vector: focus on endpoint telemetry (EDR) from affected hosts.
Timeline
What happened to this CVE, newest first.
- 2026
- Affected products added · linux/linux
- SSVC assessment updated
- Record published
- Fix documented
- Affected products added · linux/linux kernel
- CVSS changed · 5.5
- Source status changed · → Modified
- Record created in this database
- 2025
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 2× References added · Oct 15, 2026 – Oct 15, 2026
- 1× Official description updated · Oct 15, 2026 – Oct 15, 2026
References
11 on the record
- git.kernel.org/stable/c/bbc118acf7baf9e93c5e1314d14f481301af4d0f
- git.kernel.org/stable/c/8c004b7dbb340c1e5889f5fb9e5baa6f6e5303e8
- git.kernel.org/stable/c/3455607fd7be10b449f5135c00dc306b85dc0d21
- git.kernel.org/stable/c/03d8241112d5e3cccce1a01274a221099f07d2e1
- git.kernel.org/stable/c/f5e61d9b4a699dd16f32d5f39eb1cf98d84c92ed
- git.kernel.org/stable/c/35e60ec39e862159cb92923eefd5230d4a873cb9
- git.kernel.org/stable/c/f135c65085eed869d10e4e7923ce1015288618da
- git.kernel.org/stable/c/ed9afd967cbfe7da2dc0d5e52c62a778dfe9f16b
- git.kernel.org/stable/c/408bfa1489a3cfe7150b81ab0b0df99b23dd5411
- nvd.nist.gov/vuln/detail/CVE-2022-50215
- github.com/advisories/GHSA-5vwg-5h67-mq2j
Elsewhere on this site
Related CVEs (same products)
- Critical CVE-2026-99999 ipv4: validate checksum_start before completing checksum 13h
- Unknown CVE-2026-98432 ipv4: free inet_opt and ireq_opt after an RCU grace period 13h
- Unknown CVE-2026-98424 wifi: cfg80211: undo netns switch if renaming the wiphy fails 1d
- Unknown CVE-2026-98425 wifi: mac80211: don't warn when an IBSS has no channel to scan 1d
- Unknown CVE-2026-98426 wifi: mwifiex: fix IRQ leak using wrong index in MSI-X error path 1d
- Unknown CVE-2026-98427 net/sched: codel: bound the dropping loop per dequeue call 1d
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No CWE classification.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2022-50215 is "scsi: sg: Allow waiting for commands to complete on removed device", rated Medium. It affects Linux (Linux); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 5.5 describes technical severity. EPSS 0.25% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.