CVE-2026-23193
What it is
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.
At a glance
- Exploitability
- Can be exploited over the network with a low-privilege account. High risk of data exposure, data tampering, service disruption.
- Exploit odds
- 0.4% chance of exploitation in the next 30 days (EPSS).
- Fix
- A patch, advisory or fixed version is referenced. Upgrade or apply it.
Timeline
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: 0.4% in the next 30 days (EPSS).
- Severity: 8.8 HIGH (CVSS).
- Fix: a patch or advisory is linked.
Details
- Published
- Last modified
- Exploit probability
- 0.4% · EPSS, next 30 days
- Weakness
- CWE-416 · Use after free
- Record status
- Modified
Affected
- Linux Kernel < 5.10.250
- Linux Kernel < 5.15.200
- Linux Kernel < 6.1.163
- Linux Kernel < 6.6.124
- Linux Kernel < 6.12.70
- Linux Kernel < 6.18.10
- Linux Kernel 6.19
Attack profile CVSS 3.1 · 8.8
- Attack vector
- Network
- Complexity
- Low
- Privileges needed
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
Raw vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2026-23193.md and follow it. Check whether this project is affected by CVE-2026-23193. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
Fix and advisories
- https://git.kernel.org/stable/c/11ebafffce31efc6abeb28c509017976fc49f1ca
- https://git.kernel.org/stable/c/2b64015550a13bcc72910be0565548d9a754d46d
- https://git.kernel.org/stable/c/41b86a9ec037bd3435d68dd3692f0891a207e7e7
- https://git.kernel.org/stable/c/4530f4e4d0e6a207110b0ffed0c911bca43531a4
- https://git.kernel.org/stable/c/84dc6037390b8607c5551047d3970336cb51ba9a
- https://git.kernel.org/stable/c/d8dbdc146e9e9a976931b78715be2e91299049f9
- https://git.kernel.org/stable/c/fd8b0900173307039d3a84644c2fee041a7ed4fb
References
- https://git.kernel.org/stable/c/11ebafffce31efc6abeb28c509017976fc49f1ca
- https://git.kernel.org/stable/c/2b64015550a13bcc72910be0565548d9a754d46d
- https://git.kernel.org/stable/c/41b86a9ec037bd3435d68dd3692f0891a207e7e7
- https://git.kernel.org/stable/c/4530f4e4d0e6a207110b0ffed0c911bca43531a4
- https://git.kernel.org/stable/c/84dc6037390b8607c5551047d3970336cb51ba9a
- https://git.kernel.org/stable/c/d8dbdc146e9e9a976931b78715be2e91299049f9
- https://git.kernel.org/stable/c/fd8b0900173307039d3a84644c2fee041a7ed4fb