High 7.8Published Jul 19, 2026

CVE-2026-64103scsi: isci: Fix use-after-free in device removal path

Updated under an hour ago (Oct 26, 2026, 11:50 PM ET)

Does this affect you?

It affects Linux and 1 other product. Add what you run to find out whether that includes you.

No exploitation reported and no EPSS estimate yet.

Do this next

Start free and add your stack

Free account, 1 product

Every CVE for Linux

Exploited in the last 30 days

In the Linux kernel, the following vulnerability has been resolved: scsi: isci: Fix use-after-free in device removal path The ISCI completion tasklet is initialized in isci_host_alloc() (drivers/scsi/isci/init.c:496) and scheduled from both MSI-X and legacy interrupt handlers (drivers/scsi/isci/host.c:223,613). isci_host_deinit() stops the controller and waits for stop completion, but it never kills completion_tasklet before teardown continues. A top-of-function tasklet_kill() is not sufficient here: interrupts are only disabled when isci_host_stop_complete() runs, so until wait_for_stop() returns the IRQ handlers can still requeue the tasklet. The tasklet callback also re-enables interrupts after draining completions, so killing the tasklet before the source is quiesced leaves the same race open. Once wait_for_stop() returns, no further IRQ-driven scheduling can occur. Kill completion_tasklet there so teardown cannot race a queued tasklet running on a dead ihost. On remove or unload, the stale callback can otherwise dereference ihost and touch ihost->smu_registers after the host lifetime ends. A UML + KASAN analogue reproduced the failure class both with no tasklet_kill() and with tasklet_kill() placed before source quiesce, and stayed clean once the kill happened after quiescing the scheduling source. This mirrors commit f6ab594672d4 ("scsi: aic94xx: fix use-after-free in device removal path"), but ISCI needs the kill after wait_for_stop().

CVSS: 7.8 HIGH (v3.1, NVD)CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Weakness (CWE): Not given
Known exploited: Not in CISA's KEV catalog
EPSS (exploitation in the next 30 days): Not loaded for this CVE
Assigned by: Linux
NVD analysis: Analyzed
Record last updated: Jul 19, 2026
First seen by InfoSec Signals: Oct 9, 2026

Affected products

Affected products

Linux Linux linux:linux (from the name)	from 6f231dda68080759f1aed3769896e94c73099f0f before 1412995e10c74644b47f242aea6e4f3d4180e806; from 6f231dda68080759f1aed3769896e94c73099f0f before a83d3e4daba40d49324cec1c51ed261e1ea48cf1; from 6f231dda68080759f1aed3769896e94c73099f0f before ab2266601a875982f2d2033f41e070a6d5e615e2; from 6f231dda68080759f1aed3769896e94c73099f0f before 309c6058622d080fe8c2fab87c30da82d834d989; from 6f231dda68080759f1aed3769896e94c73099f0f before cb9e72c50e6c81a5903f27e0b397ce8525d7539b; from 6f231dda68080759f1aed3769896e94c73099f0f before b9ff8631006233ba246828ac70409d2cb2da38d3; 6f231dda68080759f1aed3769896e94c73099f0f builds before 6d40f2f103bb30f52f3dbadbe2c3fdf274a9763c; from 6f231dda68080759f1aed3769896e94c73099f0f before b52a8d52c3125ec9a93106ed816582368de34426	CNA record
linux linux_kernel linux:linux_kernel	from 3.0.1 before 5.10.258; from 5.11 before 5.15.209; from 5.16 before 6.1.175; from 6.2 before 6.6.142; from 6.7 before 6.12.92; from 6.13 before 6.18.34; from 6.19 before 7.0.11; 3.0; and 6 more ranges	NVD

References

References

https://git.kernel.org/stable/c/1412995e10c74644b47f242aea6e4f3d4180e806	patch
https://git.kernel.org/stable/c/a83d3e4daba40d49324cec1c51ed261e1ea48cf1	patch
https://git.kernel.org/stable/c/ab2266601a875982f2d2033f41e070a6d5e615e2	patch
https://git.kernel.org/stable/c/309c6058622d080fe8c2fab87c30da82d834d989	patch
https://git.kernel.org/stable/c/cb9e72c50e6c81a5903f27e0b397ce8525d7539b	patch
https://git.kernel.org/stable/c/b9ff8631006233ba246828ac70409d2cb2da38d3	patch
https://git.kernel.org/stable/c/6d40f2f103bb30f52f3dbadbe2c3fdf274a9763c	patch
https://git.kernel.org/stable/c/b52a8d52c3125ec9a93106ed816582368de34426	patch

The CVE record on cve.org NVD's entry

The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.