Answer in brief
CVE-2026-64103 records a High severity (CVSS 7.8) vulnerability in scsi: isci: Fix use-after-free in device removal path. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 7.8. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Product | Affected versions | Fixed versions |
|---|---|---|
| cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:3.0:-:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:3.0:rc6:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:3.0:rc7:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:7.1:rc1:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:7.1:rc2:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:7.1:rc3:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:7.1:rc4:*:*:*:*:*:* | Not reported | Not reported |
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=6f231dda68080759f1aed3769896e94c73099f0f <1412995e10c74644b47f242aea6e4f3d4180e806 || >=6f231dda68080759f1aed3769896e94c73099f0f <a83d3e4daba40d49324cec1c51ed261e1ea48cf1 || >=6f231dda68080759f1aed3769896e94c73099f0f <ab2266601a875982f2d2033f41e070a6d5e615e2 || >=6f231dda68080759f1aed3769896e94c73099f0f <309c6058622d080fe8c2fab87c30da82d834d989 || >=6f231dda68080759f1aed3769896e94c73099f0f <cb9e72c50e6c81a5903f27e0b397ce8525d7539b || >=6f231dda68080759f1aed3769896e94c73099f0f <b9ff8631006233ba246828ac70409d2cb2da38d3 || >=6f231dda68080759f1aed3769896e94c73099f0f <6d40f2f103bb30f52f3dbadbe2c3fdf274a9763c || >=6f231dda68080759f1aed3769896e94c73099f0f <b52a8d52c3125ec9a93106ed816582368de34426 | 1412995e10c74644b47f242aea6e4f3d4180e806, a83d3e4daba40d49324cec1c51ed261e1ea48cf1, ab2266601a875982f2d2033f41e070a6d5e615e2, 309c6058622d080fe8c2fab87c30da82d834d989, cb9e72c50e6c81a5903f27e0b397ce8525d7539b, b9ff8631006233ba246828ac70409d2cb2da38d3, 6d40f2f103bb30f52f3dbadbe2c3fdf274a9763c, b52a8d52c3125ec9a93106ed816582368de34426 |
| Linux/Linuxgeneric | 3.0 | Not reported |
Published upstream
Jul 19, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Nov 6, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 12, 2026
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().
Quoted source text, attributed separately from HOL analysis.