data built 2026-10-19T13:16:53Z

Look up another CVE · open CVE-2025-68324 in the interactive tracker

CVE-2025-68324

scsi: imm: Fix use-after-free bug caused by unfinished delayed work

EPSS 0.2%

Published 2025-12-18 (10 months ago) by the Linux kernel CNA. Subsystem drivers/scsi. Debian urgency: not yet assigned.

Debian does not build this code. The per-release build detail is under "Where it lives" below.

What to do, per Debian release

Debian's own status for CVE-2025-68324 in every release this site tracks, and what each one means in practice. Every status below is the one the Debian Security Team publishes for this CVE. source

ReleaseStatus VersionWhat this means
Debian 12bookwormvulnerable6.1.190-1No fix published anywhere yet, neither in Debian nor upstream for the series bookworm tracks. Watch the Debian tracker page for this CVE. Advisories for bookworm have historically landed a median of 23 days after publication.
Debian 13trixiefixed6.12.63-1Update the kernel and reboot. Fixed in 6.12.63-1. A running kernel keeps the old code until the machine restarts.
Debian 14forkyfixed6.17.13-1Update the kernel and reboot. Fixed in 6.17.13-1. A running kernel keeps the old code until the machine restarts.
Debian unstablesidfixed6.17.13-1Update the kernel and reboot. Fixed in 6.17.13-1. A running kernel keeps the old code until the machine restarts.

The vulnerability

What the bug is

The delayed work item 'imm_tq' is initialized in imm_attach() and scheduled via imm_queuecommand() for processing SCSI commands. When the IMM parallel port SCSI host adapter is detached through imm_detach(), the imm_struct device instance is deallocated. However, the delayed work might still be pending or executing when imm_detach() is called, leading to use-after-free bugs when the work function imm_interrupt() accesses the already freed imm_struct memory. The race condition can occur as follows: CPU 0(detach thread) | CPU 1 | imm_queuecommand() | imm_queuecommand_lck() imm_detach() | schedule_delayed_work() kfree(dev) //FREE | imm_interrupt() | dev = container_of(...) //USE dev-> //USE Add disable_delayed_work_sync() in imm_detach() to guarantee proper cancellation of the delayed work item before imm_struct is deallocated.

Where it lives

The fix touches these files. If the subsystem is one you do not use, the practical exposure is lower, though the package is still the vulnerable one.

drivers/scsi/imm.c

What this is
SCSI SUBSYSTEMMAINTAINERS section matched on drivers/scsi/ · linux-scsi@vger.kernel.org · Maintained
Kernel module
none to look for. The file would have gone into imm, and Debian does not compile it into that module, so finding imm in lsmod would say nothing about this CVE.

Check it on the machine

grep -w CONFIG_SCSI_IMM /boot/config-$(uname -r)

Reads the booted kernel's own configuration, on the machine and nowhere else. =y is built in, =m is a module, and an is not set line means the code is not there.

Show whether Debian builds this, per release

Debian does not build this code. In 4 releases below, every kernel flavour Debian publishes has the switch off, so the vulnerable file is compiled into no kernel binary Debian ships.

  • bookworm, trixie, forky, sidn
n
not enabled on any flavour - this release does not build the code
Build switch
CONFIG_SCSI_IMM

From the configuration Debian publishes for every kernel flavour it builds. It covers only the architectures Debian ships a linux-config package for, and nothing about a kernel you built yourself. Debian's own status above stays authoritative about the source package.MAINTAINERS kbuild Makefiles Debian linux-config packages

Signals

Published
2025-12-18 (10 months ago)source
CVSS
no vector published, unrated
Attack vector
not published
EPSS
0.19%, higher than 7.8% of all CVEssource
CISA KEV
not listedthe KEV catalogue
Debian urgency
not yet assignedsource
Subsystem
drivers/scsi

Upstream fixes

The versions the CNA records as introducing and fixing this, and the commit for each. source

IntroducedFixed inCommit
2.6.126.12.6331ab2aad7a7b
2.6.126.17.1348dd41fa2d6c
2.6.126.18.29e434426cc23
2.6.126.19ab58153ec64f

Why the CNA scored it this way

The kernel CNA published no CVSS vector and no reasoning for CVE-2025-68324, which is why it is shown as unrated rather than given an invented score. 6,405 of the 20,413 CVEs here carry reasoning; this is not one of them.