GPU VulnDB

Database/Control plane, storage & DevOps

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

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

Impact

iscsit_dec_conn_usage_count() invokes complete() while holding conn->conn_usage_lock; the waiter, typically iscsit_close_connection(), can free the iscsit_conn structure before the first thread reaches spin_unlock_bh(), giving a KASAN slab-use-after-free. This is the connection-level counterpart of the session-level bug, with a separate fix and a separate code path, so it is tracked on its own. For an operator it means the LIO iSCSI target serving block storage to the fleet can crash on connection teardown, dropping LUNs for every initiator on that head. The record shows a crash, not a demonstrated escalation.

Who can reach it

Reachable from the iSCSI data path: an initiator that opens and closes connections against the target exercises the refcount path. The record does not state whether authentication is required; in practice it depends on the target's initiator ACLs and CHAP settings.

What to do

Update the kernel on iSCSI target hosts to a build with the conn_usage_lock fix (commits in the record) and reboot the target, failing over to an HA peer first where one exists. Tighten initiator ACLs until the reboot can be scheduled. The record names no fixed release beyond the listed commits.

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.