CVE-2026-23216: scsi: target: iscsi: Fix use-after-free in iscsit_dec_conn_usage_count()

Published Feb 18, 2026
·
Updated

In the Linux kernel, the following vulnerability has been resolved:

scsi: target: iscsi: Fix use-after-free in iscsitdecconnusagecount()

In iscsitdecconnusagecount(), the function calls complete() while holding the conn->connusagelock. As soon as complete() is invoked, the waiter (such as iscsitcloseconnection()) may wake up and proceed to free the iscsitconn structure.

If the waiter frees the memory before the current thread reaches spinunlockbh(), it results in a KASAN slab-use-after-free as the function attempts to release a lock within the already-freed connection structure.

Fix this by releasing the spinlock before calling complete().

Affected Software

14 affected componentsFixes available
Linux Linux kernel
Microsoft azl3 kernel 6.6.121.1-1
Linux Linux kernel>=3.1<5.10.250
Linux Linux kernel>=5.11<5.15.200
Linux Linux kernel>=5.16<6.1.163
Linux Linux kernel>=6.2<6.6.124
Linux Linux kernel>=6.7<6.12.70
Linux Linux kernel>=6.13<6.18.10
Linux Linux kernel=6.19-rc1
Linux Linux kernel=6.19-rc2
Linux Linux kernel=6.19-rc3
Linux Linux kernel=6.19-rc4
Linux Linux kernel=6.19-rc5
Linux Linux kernel=6.19-rc6

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Configuration

    Modify iscsit_dec_conn_usage_count() so it releases the conn_usage_lock (via spin_unlock_bh()) before calling complete(), preventing KASAN slab-use-after-free when a waiter frees the iscsit_conn structure early.

    Linux kernel (scsi target iscsi) spinlock release order in iscsit_dec_conn_usage_count() = Release conn->conn_usage_lock spinlock (spin_unlock_bh()) before invoking complete()

Event History

Feb 18, 2026
CVE Published
via MITRE·02:21 PM
Data Sourced
via MITRE·02:21 PM
Description
Data Sourced
via Red Hat·03:02 PM
DescriptionSeverityAffected Software
Data Sourced
via NVD·03:18 PM
RemedyDescriptionSeverityWeaknessAffected Software
Feb 21, 2026
Data Sourced
via Microsoft·12:26 PM
DescriptionSeverityWeaknessAffected Software
Updated
via Microsoft·12:26 PM
DescriptionSeverity

Frequently Asked Questions

1

What is the severity of CVE-2026-23216?

CVE-2026-23216 has been classified with a medium severity due to potential use-after-free vulnerabilities in the Linux kernel.

2

How do I fix CVE-2026-23216?

To fix CVE-2026-23216, update your Linux kernel to the latest stable version where the vulnerability has been patched.

3

What components are affected by CVE-2026-23216?

CVE-2026-23216 affects the SCSI target implementation in the Linux kernel, particularly the iscsi subsystem.

4

Is there any exploit available for CVE-2026-23216?

As of now, there are no publicly disclosed exploits specifically targeting CVE-2026-23216.

5

What are the potential impacts of CVE-2026-23216?

The potential impacts of CVE-2026-23216 include system instability or crashes due to use-after-free conditions in connection handling.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203