GPU VulnDB

Database/Control plane, storage & DevOps

Linux kernel iSCSI target: use-after-free on session teardown when complete() is called under the lock

CVSS 7.8CVE-2026-23193Control plane, storage & DevOpscurated

Impact

iscsit_dec_session_usage_count() calls complete() while still holding sess->session_usage_lock. The waiter on the session release path can wake, free the iscsit_session structure, and leave the first thread unlocking a spinlock inside freed memory - a KASAN slab-use-after-free. This lives in the in-kernel iSCSI target (LIO), so it affects storage servers exporting block volumes to a GPU fleet, not the GPU nodes. The practical outcome is a crash of the storage head during session teardown, which drops every initiator's volumes at once; the record does not demonstrate controlled exploitation.

Who can reach it

Reachable from the iSCSI data path: an initiator that can open and tear down sessions against the target drives the refcount path. Whether an unauthenticated initiator can reach it depends on the target's ACLs and CHAP configuration; the record does not state authentication requirements.

What to do

Update the kernel on iSCSI target hosts to a build containing the session_usage_lock fix (commits in the record) and reboot the target, failing over to the HA peer first if there is one - an iSCSI target reboot drops all exported LUNs. Restrict initiator ACLs to known hosts in the meantime. No fixed release version is named beyond the listed commits. Closely related to the connection-count variant fixed separately.

References

Related entries

All Control plane, storage & DevOps entries

This entry is curated: imported from vendor advisories with machine assistance, not yet individually verified. Confirm against your vendor's advisory before acting, and report anything wrong.