Skip to main content
VulnerabilityPublished Updated

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

Affects Linux kernelSource CVE Database V5

0

Not known to be exploited · fixed in ba684191437380a07b27666eb4e72748be1ea201 : update Linux kernel when convenient.

Data as of 26 Oct 2026, 13:47 UTC

Severity
Unrated

Rated by Threat Radar · No CVSS score from NVD or the CNA

EPSS
0.1% chance of exploitation in 30 days – higher than 3% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CISA SSVC
Exploitation
No evidence of active exploitation and no public proof of concept
Automatable
Attackers cannot reliably automate steps 1–4 of the kill chain
Technical impact
Total control over the software or total information disclosure

CISA SSVC assessment, 2026-06-10.

Patch
Available – fixed in ba684191437380a07b27666eb4e72748be1ea201, 275016a551ba1a068a3bd6171b18611726b67110, 9411a89e9e7135cc459178fa77a3f1d6191ae903 +4

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 18 Feb 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ e48354ce078c079996f89d715dfa44814b4eba01, < ba684191437380a07b27666eb4e72748be1ea201
Fixed in
  • ba684191437380a07b27666eb4e72748be1ea201
LinuxLinuxAffected
  • ≥ e48354ce078c079996f89d715dfa44814b4eba01, < 275016a551ba1a068a3bd6171b18611726b67110
Fixed in
  • 275016a551ba1a068a3bd6171b18611726b67110
LinuxLinuxAffected
  • ≥ e48354ce078c079996f89d715dfa44814b4eba01, < 9411a89e9e7135cc459178fa77a3f1d6191ae903
Fixed in
  • 9411a89e9e7135cc459178fa77a3f1d6191ae903
LinuxLinuxAffected
  • ≥ e48354ce078c079996f89d715dfa44814b4eba01, < 8518f072fc92921418cd9ed4268dd4f3e9a8fd75
Fixed in
  • 8518f072fc92921418cd9ed4268dd4f3e9a8fd75
LinuxLinuxAffected
  • ≥ e48354ce078c079996f89d715dfa44814b4eba01, < 3835e49e146a4e6e7787b29465f1a23379b6ec44
Fixed in
  • 3835e49e146a4e6e7787b29465f1a23379b6ec44
LinuxLinuxAffected
  • ≥ e48354ce078c079996f89d715dfa44814b4eba01, < 73b487d44bf4f92942629d578381f89c326ff77f
Fixed in
  • 73b487d44bf4f92942629d578381f89c326ff77f

Description

In the Linux kernel, the following vulnerability has been resolved: scsi: target: iscsi: Fix use-after-free in iscsit_dec_conn_usage_count() In iscsit_dec_conn_usage_count(), the function calls complete() while holding the conn->conn_usage_lock. As soon as complete() is invoked, the waiter (such as iscsit_close_connection()) may wake up and proceed to free the iscsit_conn structure. If the waiter frees the memory before the current thread reaches spin_unlock_bh(), 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().

References

Community reviews

Loading reviews…