CVE-2025-68324: Linux kernel · scsi: imm: Fix use-after-free bug caused by unfinished delayed work
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in ab58153ec64fa3fc9aea09ca09dc9322e0b54a7c : update Linux kernel when convenient.
Data as of 26 Oct 2026, 13:47 UTC
Rated by Threat Radar · No CVSS score from NVD or the CNA
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 12% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in ab58153ec64fa3fc9aea09ca09dc9322e0b54a7c, 48dd41fa2d6c6a0c50e714deeba06ffe7f91961b, 31ab2aad7a7b7501e904a09bf361e44671f66092 +2
Exploitation evidence
Disclosed: evidence found.
CVE published 18 Dec 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in– |
Description
In the Linux kernel, the following vulnerability has been resolved: scsi: imm: Fix use-after-free bug caused by unfinished delayed work 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.
References
- git.kernel.org/stable/c/9a8e53154353580d53f7f86a253927e41294017e (opens in a new tab)
- git.kernel.org/stable/c/31ab2aad7a7b7501e904a09bf361e44671f66092 (opens in a new tab)
- git.kernel.org/stable/c/48dd41fa2d6c6a0c50e714deeba06ffe7f91961b (opens in a new tab)
- git.kernel.org/stable/c/9e434426cc23ad5e2aad649327b59aea00294b13 (opens in a new tab)
- git.kernel.org/stable/c/ab58153ec64fa3fc9aea09ca09dc9322e0b54a7c (opens in a new tab)