CVE-2023-53586: scsi: target: Fix multiple LUN_RESET handling
Noroxi assessment
Priority: Monitor (action score 18/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.45% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. Special conditions such as timing or configuration are required.
- Fixed version: Linux Linux 2c43de56f9220dca3e28c774d1c5e2cab574223a, 673db054d7a2b5a470d7a25baf65956d005ad729, 9158c86fd3237acaea8f0181c7836d90fd6eea10.
- Severity is disputed: the assigning authority (CNA) scores it 8.8, NVD 4.7.
Low priority for now. Upgrade to Linux Linux 2c43de56f9220dca3e28c774d1c5e2cab574223a, 673db054d7a2b5a470d7a25baf65956d005ad729, 9158c86fd3237acaea8f0181c7836d90fd6eea10 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: target: Fix multiple LUN_RESET handling This fixes a bug where an initiator thinks a LUN_RESET has cleaned up running commands when it hasn't. The bug was added in commit 51ec502a3266 ("target: Delete tmr from list before processing"). The problem occurs when: 1. We have N I/O cmds running in the target layer spread over 2 sessions. 2. The initiator sends a LUN_RESET for each session. 3. session1's LUN_RESET loops over all the running commands from both sessions and moves them to its local drain_task_list. 4. session2's LUN_RESET does not see the LUN_RESET from session1 because the commit above has it remove itself. session2 also does not see any commands since the other reset moved them off the state lists. 5. sessions2's LUN_RESET will then complete with a successful response. 6. sessions2's inititor believes the running commands on its session are now cleaned up due to the successful response and cleans up the running commands from its side. It then restarts them. 7. The commands do eventually complete on the backend and the target starts to return aborted task statuses for them. The initiator will either throw a invalid ITT error or might accidentally lookup a new task if the ITT has been reallocated already. Fix the bug by reverting the patch, and serialize the execution of LUN_RESETs and Preempt and Aborts. Also prevent us from waiting on LUN_RESETs in core_tmr_drain_tmr_list, because it turns out the original patch fixed a bug that was not mentioned. For LUN_RESET1 core_tmr_drain_tmr_list can see a second LUN_RESET and wait on it. Then the second reset will run core_tmr_drain_tmr_list and see the first reset and wait on it resulting in a deadlock.
- Published
- Oct 4, 2025
- Updated
- Aug 5, 2026
- EPSS
- 0.4% · 39th percentile
- CWE
- CWE-415
Report tools
Action score
18
Monitor
Low priority for now.
- CVSS
- 18 / 40 · 4.7 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.4%
CNA vs NVD score
- NVD
- 4.7
- CNA · Linux
- 8.8
- 4.1 point gap
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
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 kernel4.11 and later · before 5.10.180
- linux linux kernel5.11 and later · before 5.15.111
- linux linux kernel5.16 and later · before 6.1.28
- linux linux kernel6.2 and later · before 6.2.15
- linux linux kernel6.3 and later · before 6.3.2
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
- 4.11affected
- 51ec502a32665fed66c7f03799ede4023b212536 and later · before e1f59cd18a10969d08a082264b557876ca38766eaffected · git
- 51ec502a32665fed66c7f03799ede4023b212536 and later · before 9158c86fd3237acaea8f0181c7836d90fd6eea10affected · git
- 51ec502a32665fed66c7f03799ede4023b212536 and later · before eacfe32c3650bfd0e54224d160c431013d7f6998affected · git
- 51ec502a32665fed66c7f03799ede4023b212536 and later · before ed18526289b5603bf2253dee50f1d7ec245cf397affected · git
- 51ec502a32665fed66c7f03799ede4023b212536 and later · before 2c43de56f9220dca3e28c774d1c5e2cab574223aaffected · git
- 51ec502a32665fed66c7f03799ede4023b212536 and later · before 673db054d7a2b5a470d7a25baf65956d005ad729affected · git
- before 4.11not affected · semver
- 5.10.180 and later · up to and including 5.10.*not affected · semver
- 5.15.111 and later · up to and including 5.15.*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 6.1.37-1 | 6.1.37-1 |
| Debian:13 | linux | before 6.3.7-1 | 6.3.7-1 |
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-2023-53584Oct 4, 2025 · ubifs: ubifs_releasepage: Remove ubifs_assert(0) to valid this process22Monitor
- ← EarlierCVE-2023-53585Oct 4, 2025 · bpf: reject unhashed sockets in bpf_sk_assign22Monitor
- Later →CVE-2023-53588Oct 4, 2025 · wifi: mac80211: check for station first in client probe22Monitor
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 | 2c43de56f9220dca3e28c774d1c5e2cab574223a | Vendor (CNA) |
| Linux Linux | 673db054d7a2b5a470d7a25baf65956d005ad729 | Vendor (CNA) |
| Linux Linux | 9158c86fd3237acaea8f0181c7836d90fd6eea10 | Vendor (CNA) |
| Linux Linux | e1f59cd18a10969d08a082264b557876ca38766e | Vendor (CNA) |
| Linux Linux | eacfe32c3650bfd0e54224d160c431013d7f6998 | Vendor (CNA) |
| Linux Linux | ed18526289b5603bf2253dee50f1d7ec245cf397 | Vendor (CNA) |
| debian:linux | 6.1.37-1 · Debian:12 | Package registry (OSV) |
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.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
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.
- CVE-2026-31608202 days apartsmb: server: avoid double-free in smb_direct_free_sendmsg after smb_direct_flush_send_list()39Monitor
- CVE-2026-31609202 days apartsmb: client: avoid double-free in smbd_free_send_io() after smbd_send_batch_flush()39Monitor
- CVE-2026-43011209 days apartnet/x25: Fix potential double free of skb39Monitor
- CVE-2026-43414216 days apartscsi: qla2xxx: Completely fix fcport double free39Monitor
- CVE-2026-52993263 days aparttipc: fix double-free in tipc_buf_append()39Monitor
- CVE-2026-63888288 days apartscsi: target: iscsi: Fix CRC overread and double-free in iscsit_handle_text_cmd()39Monitor
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).
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- Special conditions such as timing or configuration are required.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- High
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-415 · Double FreeCVSS vector
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (5 more)Show less
- git.kernel.org/stable/c/673db054d7a2b5a470d7a25baf65956d005ad729
- git.kernel.org/stable/c/9158c86fd3237acaea8f0181c7836d90fd6eea10
- git.kernel.org/stable/c/e1f59cd18a10969d08a082264b557876ca38766e
- git.kernel.org/stable/c/eacfe32c3650bfd0e54224d160c431013d7f6998
- git.kernel.org/stable/c/ed18526289b5603bf2253dee50f1d7ec245cf397
Vendor advisories and official records. Exploit/PoC links are deliberately left out.