CVE-2026-64103

Vulnérabilité non évaluée dans Linux (Linux)

CVSS 0.0 · Non évaluée
EPSS 0.1%
Linux•Linux•Versions : <=6.1.*, <=7.0.*, 3.0, <=6.12.*, <309c6058622d080fe8c2fab87c30da82d834d989, 0, <ab2266601a875982f2d2033f41e070a6d5e615e2, 5.15.209, 6.12.92, 6.6.142, <=5.10.*, <=6.6.*, 6.1.175, 6f231dda68080759f1aed3769896e94c73099f0f, <6d40f2f103bb30f52f3dbadbe2c3fdf274a9763c, 6.18.34, 7.1, <=6.18.*, 7.0.11, 5.10.258, <1412995e10c74644b47f242aea6e4f3d4180e806, <a83d3e4daba40d49324cec1c51ed261e1ea48cf1, <3.0, <=*, <cb9e72c50e6c81a5903f27e0b397ce8525d7539b, <=5.15.*, <b9ff8631006233ba246828ac70409d2cb2da38d3, <b52a8d52c3125ec9a93106ed816582368de34426

Description

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

Gravité et risque d'exploitation

CVE-2026-64103 obtient un score CVSS de 0.0/10, soit une gravité non évaluée. Selon le modèle EPSS, la probabilité qu'elle soit exploitée dans les 30 prochains jours est de 0.13 %, ce qui la place devant 2.0 % des CVE référencées.

Que faire ?

  • Vérifiez si Linux (versions <=6.1.*, <=7.0.*, 3.0, <=6.12.*, <309c6058622d080fe8c2fab87c30da82d834d989, 0, <ab2266601a875982f2d2033f41e070a6d5e615e2, 5.15.209, 6.12.92, 6.6.142, <=5.10.*, <=6.6.*, 6.1.175, 6f231dda68080759f1aed3769896e94c73099f0f, <6d40f2f103bb30f52f3dbadbe2c3fdf274a9763c, 6.18.34, 7.1, <=6.18.*, 7.0.11, 5.10.258, <1412995e10c74644b47f242aea6e4f3d4180e806, <a83d3e4daba40d49324cec1c51ed261e1ea48cf1, <3.0, <=*, <cb9e72c50e6c81a5903f27e0b397ce8525d7539b, <=5.15.*, <b9ff8631006233ba246828ac70409d2cb2da38d3, <b52a8d52c3125ec9a93106ed816582368de34426) est présent sur votre parc.
  • Appliquez le correctif ou la version corrigée indiqués dans les références de l'éditeur.
  • À défaut de correctif, limitez l'exposition (filtrage réseau, désactivation du composant).
  • Automatisez la détection : les agents CVE Heimdall (gratuits, open source) corrèlent l'inventaire de vos serveurs avec la base CVE.

Références