CVE-2026-23216
What it is
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().
At a glance
- Exploitability
- Can be exploited locally on the machine with a low-privilege account. High risk of data exposure, data tampering, service disruption.
- Exploit odds
- 0.1% chance of exploitation in the next 30 days (EPSS).
- Fix
- A patch, advisory or fixed version is referenced. Upgrade or apply it.
Timeline
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: 0.1% in the next 30 days (EPSS).
- Severity: 7.8 HIGH (CVSS).
- Fix: a patch or advisory is linked.
Details
- Published
- Last modified
- Exploit probability
- 0.1% · EPSS, next 30 days
- Weakness
- CWE-416 · Use after free
- Record status
- Modified
Affected
- Linux Kernel < 5.10.250
- Linux Kernel < 5.15.200
- Linux Kernel < 6.1.163
- Linux Kernel < 6.6.124
- Linux Kernel < 6.12.70
- Linux Kernel < 6.18.10
- Linux Kernel 6.19
Attack profile CVSS 3.1 · 7.8
- Attack vector
- Local
- Complexity
- Low
- Privileges needed
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
Raw vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2026-23216.md and follow it. Check whether this project is affected by CVE-2026-23216. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
Fix and advisories
- https://git.kernel.org/stable/c/275016a551ba1a068a3bd6171b18611726b67110
- https://git.kernel.org/stable/c/3835e49e146a4e6e7787b29465f1a23379b6ec44
- https://git.kernel.org/stable/c/48fe983e92de2c59d143fe38362ad17ba23ec7f3
- https://git.kernel.org/stable/c/73b487d44bf4f92942629d578381f89c326ff77f
- https://git.kernel.org/stable/c/8518f072fc92921418cd9ed4268dd4f3e9a8fd75
- https://git.kernel.org/stable/c/9411a89e9e7135cc459178fa77a3f1d6191ae903
- https://git.kernel.org/stable/c/ba684191437380a07b27666eb4e72748be1ea201
References
- https://git.kernel.org/stable/c/275016a551ba1a068a3bd6171b18611726b67110
- https://git.kernel.org/stable/c/3835e49e146a4e6e7787b29465f1a23379b6ec44
- https://git.kernel.org/stable/c/48fe983e92de2c59d143fe38362ad17ba23ec7f3
- https://git.kernel.org/stable/c/73b487d44bf4f92942629d578381f89c326ff77f
- https://git.kernel.org/stable/c/8518f072fc92921418cd9ed4268dd4f3e9a8fd75
- https://git.kernel.org/stable/c/9411a89e9e7135cc459178fa77a3f1d6191ae903
- https://git.kernel.org/stable/c/ba684191437380a07b27666eb4e72748be1ea201