CVE-2026-23193: Linux kernel · scsi: target: iscsi: Fix use-after-free in iscsit_dec_session_usage_count()
Affects Linux kernelSource CVE Database V5
Not known to be exploited · CVSS 8.8 High · fixed in fd8b0900173307039d3a84644c2fee041a7ed4fb : patch Linux kernel soon.
Data as of 26 Oct 2026, 10:12 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 29% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- CISA SSVC
- Exploitation
- No evidence of active exploitation and no public proof of concept
- Automatable
- Attackers cannot reliably automate steps 1–4 of the kill chain
- Technical impact
- Total control over the software or total information disclosure
CISA SSVC assessment, 2026-06-16.
- Patch
- Available – fixed in fd8b0900173307039d3a84644c2fee041a7ed4fb, d8dbdc146e9e9a976931b78715be2e91299049f9, 4530f4e4d0e6a207110b0ffed0c911bca43531a4 +4
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 14 Feb 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
Description
In the Linux kernel, the following vulnerability has been resolved: scsi: target: iscsi: Fix use-after-free in iscsit_dec_session_usage_count() In iscsit_dec_session_usage_count(), the function calls complete() while holding the sess->session_usage_lock. Similar to the connection usage count logic, the waiter signaled by complete() (e.g., in the session release path) may wake up and free the iscsit_session structure immediately. This creates a race condition where the current thread may attempt to execute spin_unlock_bh() on a session structure that has already been deallocated, resulting in a KASAN slab-use-after-free. To resolve this, release the session_usage_lock before calling complete() to ensure all dereferences of the sess pointer are finished before the waiter is allowed to proceed with deallocation.
References
- git.kernel.org/stable/c/2b64015550a13bcc72910be0565548d9a754d46d (opens in a new tab)
- git.kernel.org/stable/c/fd8b0900173307039d3a84644c2fee041a7ed4fb (opens in a new tab)
- git.kernel.org/stable/c/d8dbdc146e9e9a976931b78715be2e91299049f9 (opens in a new tab)
- git.kernel.org/stable/c/11ebafffce31efc6abeb28c509017976fc49f1ca (opens in a new tab)
- git.kernel.org/stable/c/41b86a9ec037bd3435d68dd3692f0891a207e7e7 (opens in a new tab)
- git.kernel.org/stable/c/4530f4e4d0e6a207110b0ffed0c911bca43531a4 (opens in a new tab)
- git.kernel.org/stable/c/84dc6037390b8607c5551047d3970336cb51ba9a (opens in a new tab)