CVE-2026-64103

published 19 Jul 2026 · updated 14 Nov 2026

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

7.8HighCVSS 7.8EPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 5.10.258, Kernel 5.15.209, Kernel 6.1.175 and 12 more.

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().

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
LinuxKernel>=3.0.1 <5.10.258, >=5.11 <5.15.209, >=5.16 <6.1.175, >=6.13 <6.18.34, >=6.19 <7.0.11, >=6.2 <6.6.142, >=6.7 <6.12.92, =3.0, =7.1, >=6f231dda68080759f1aed3769896e94c73099f0f <309c6058622d080fe8c2fab87c30da82d834d989, >=6f231dda68080759f1aed3769896e94c73099f0f <6d40f2f103bb30f52f3dbadbe2c3fdf274a9763c, >=6f231dda68080759f1aed3769896e94c73099f0f <a83d3e4daba40d49324cec1c51ed261e1ea48cf1, >=6f231dda68080759f1aed3769896e94c73099f0f <ab2266601a875982f2d2033f41e070a6d5e615e2, >=6f231dda68080759f1aed3769896e94c73099f0f <b52a8d52c3125ec9a93106ed816582368de34426, >=6f231dda68080759f1aed3769896e94c73099f0f <b9ff8631006233ba246828ac70409d2cb2da38d3, >=6f231dda68080759f1aed3769896e94c73099f0f <cb9e72c50e6c81a5903f27e0b397ce8525d7539b, >=6f231dda68080759f1aed3769896e94c73099f0f <1412995e10c74644b47f242aea6e4f3d4180e8065.10.258, 5.15.209, 6.1.175, 6.18.34, 7.0.11, 6.6.142, 6.12.92, 309c6058622d080fe8c2fab87c30da82d834d989, 6d40f2f103bb30f52f3dbadbe2c3fdf274a9763c, a83d3e4daba40d49324cec1c51ed261e1ea48cf1, ab2266601a875982f2d2033f41e070a6d5e615e2, b52a8d52c3125ec9a93106ed816582368de34426, b9ff8631006233ba246828ac70409d2cb2da38d3, cb9e72c50e6c81a5903f27e0b397ce8525d7539b, 1412995e10c74644b47f242aea6e4f3d4180e806
linux-kernel: Kernel>=3.0.0 <5.10.258, >=5.11.0 <5.15.209, >=5.16.0 <6.1.175, >=6.13.0 <6.18.34, >=6.19.0 <7.0.11, >=6.2.0 <6.6.142, >=6.7.0 <6.12.925.10.258, 5.15.209, 6.1.175, 6.18.34, 7.0.11, 6.6.142, 6.12.92

Timeline

Every event on this vulnerability

Related

Other vulnerabilities in Kernel, strongest first

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-64103 severity on Zeptric[![CVE-2026-64103](https://zeptric.io/badge/cve/CVE-2026-64103.svg)](https://zeptric.io/cve/CVE-2026-64103)