CVE-2026-64103

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