Monitor vulnerabilities like this one.
Sign up free to get alerted when software you use is affected.
Linux Kernel: Incorrect Locking in iSCSI Session Management
CVE-2026-23193
Summary
A bug in the Linux kernel's iSCSI session management could cause a program to crash or behave unexpectedly. This has been fixed in the latest Linux kernel updates, so it's essential to apply the latest patches to prevent potential issues. If you use the iSCSI protocol, you should update your Linux kernel as soon as possible.
Original title
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 c...
Original 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.
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.
- 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
Published: 14 Feb 2026 · Updated: 10 Mar 2026 · First seen: 6 Mar 2026