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-2025-68324scsi: imm: Fix use-after-free bug caused by unfinished delayed work

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.

Timeline

  1. ID reserved

    By Linux

  2. · 2 days later

    Published

  3. · 11 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

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Deferred.

EPSS (exploitation in 30 days)
0.23% · top 86% of all CVEs (12 Nov 2026)
Loading the EPSS history…

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

Affected products

  • Linux · Linux

    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < cfd561e8df5f46fc1c9d54885165a60e63831c14
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 9a8e53154353580d53f7f86a253927e41294017e
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 31ab2aad7a7b7501e904a09bf361e44671f66092
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 48dd41fa2d6c6a0c50e714deeba06ffe7f91961b
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 9e434426cc23ad5e2aad649327b59aea00294b13
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < ab58153ec64fa3fc9aea09ca09dc9322e0b54a7c
  • Linux · Linux

    • affected 2.6.12
    • unaffected < 2.6.12
    • unaffected 6.1.191 – ≤ 6.1.*
    • unaffected 6.6.160 – ≤ 6.6.*
    • unaffected 6.12.63 – ≤ 6.12.*
    • unaffected 6.17.13 – ≤ 6.17.*
    • unaffected 6.18.2 – ≤ 6.18.*
    • unaffected 6.19 – ≤ *

References

References6

Sources

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

Badge for a README or a ticket

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

Record last updated .