CVE-2026-23193: scsi: target: iscsi: Fix use-after-free in iscsit_dec_session_usage_count()
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.
Security readout for executives and security teams
Plain-English summary
A race in the Linux kernel’s iSCSI target session cleanup can access a session after it has been freed. This may crash the system or potentially compromise confidentiality and integrity, as reflected by the supplied CVSS assessment. The sources do not establish remote code execution or real-world exploitation.
Executive priority
Treat as a high-priority update for exposed or business-critical iSCSI target servers. Other Linux systems should first be checked for use of the affected subsystem. Accelerate remediation where storage availability is important, but do not characterize this as actively exploited based on the supplied evidence.
Technical view
iscsit_dec_session_usage_count() called complete() while holding session_usage_lock. The awakened release waiter could immediately free iscsit_session, leaving the original thread to call spin_unlock_bh() through freed memory. The fix releases the lock before signaling completion, ensuring session dereferences finish before deallocation can proceed.
Likely exposure
Exposure is most likely on Linux systems using the kernel iSCSI target functionality. The CVSS vector describes network reachability, low complexity, low privileges, and no user interaction. The supplied version data is ambiguous and should not be used alone to determine whether a distribution kernel is vulnerable.
Exploitation context
The bundle marks this CVE as absent from KEV and provides no evidence of active exploitation or a public exploit. KASAN detected the slab use-after-free. Although CVSS 8.8 models high confidentiality, integrity, and availability impact, the sources do not demonstrate reliable exploitation beyond triggering the race.
Researcher notes
The vulnerable ordering permits completion wake-up before the current thread has finished using sess. Stable fixes reorder operations so spin_unlock_bh() occurs before complete(). Seven kernel.org commits are supplied, apparently covering stable branches, but the bundle does not map each commit to a specific version or distribution package.
Mitigation direction
Install a vendor-supported kernel containing the applicable stable fix for your kernel branch.
Prioritize systems providing iSCSI target services, especially those reachable by untrusted or minimally privileged clients.
Restrict iSCSI target network access and credentials while awaiting the appropriate kernel update.
Check Linux distribution advisories for exact package versions and reboot requirements.
Validation and detection
Inventory systems configured to provide Linux kernel iSCSI target services.
Compare each running kernel package against its distribution’s CVE advisory or fixed package version.
Confirm the applicable stable fix is present in vendor changelogs or kernel source history.
After updating, verify the fixed kernel is running and iSCSI services operate normally.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2026-23193 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
3Timeline events
1ADP providers
8Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.