Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

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

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

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 4 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2026-64103, by who scored it
Scored byCVSSScoreVector
NVDNVD · Analyzed3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS (exploitation in 30 days)
0.13% · top 98% of all CVEs (14 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.8.

Affected products

  • Linux · Linux

    • affected 6f231dda68080759f1aed3769896e94c73099f0f – < 1412995e10c74644b47f242aea6e4f3d4180e806
    • affected 6f231dda68080759f1aed3769896e94c73099f0f – < a83d3e4daba40d49324cec1c51ed261e1ea48cf1
    • affected 6f231dda68080759f1aed3769896e94c73099f0f – < ab2266601a875982f2d2033f41e070a6d5e615e2
    • affected 6f231dda68080759f1aed3769896e94c73099f0f – < 309c6058622d080fe8c2fab87c30da82d834d989
    • affected 6f231dda68080759f1aed3769896e94c73099f0f – < cb9e72c50e6c81a5903f27e0b397ce8525d7539b
    • affected 6f231dda68080759f1aed3769896e94c73099f0f – < b9ff8631006233ba246828ac70409d2cb2da38d3
    • affected 6f231dda68080759f1aed3769896e94c73099f0f – < 6d40f2f103bb30f52f3dbadbe2c3fdf274a9763c
    • affected 6f231dda68080759f1aed3769896e94c73099f0f – < b52a8d52c3125ec9a93106ed816582368de34426
  • Linux · Linux

    • affected 3.0
    • unaffected < 3.0
    • unaffected 5.10.258 – ≤ 5.10.*
    • unaffected 5.15.209 – ≤ 5.15.*
    • unaffected 6.1.175 – ≤ 6.1.*
    • unaffected 6.6.142 – ≤ 6.6.*
    • unaffected 6.12.92 – ≤ 6.12.*
    • unaffected 6.18.34 – ≤ 6.18.*
    • unaffected 7.0.11 – ≤ 7.0.*
    • unaffected 7.1 – ≤ *

References

References8

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-64103 badge
[![CVE-2026-64103](https://cveledger.app/badge/CVE-2026-64103.svg)](https://cveledger.app/cve/CVE-2026-64103)

Record last updated .