CVE-2026-99456
scsi: dc395x: sync the waiting_timer before freeing the host
What happened?
In the Linux kernel, the following vulnerability has been resolved:
scsi: dc395x: sync the waiting_timer before freeing the host
The waiting_timer callback re-arms itself and takes the host lock. adapter_uninit() currently stops it with timer_delete(), which does not wait for a callback already running on another CPU. The final scsi_host_put() that frees the host (and the host lock the callback dereferences) runs right after adapter_uninit(), so a concurrent or just re-armed callback can fire after the free, leaving a potential use-after-free window.
Replace timer_delete() with timer_shutdown_sync() at the top of adapter_uninit(), before the host-lock section: the timer is dequeued, a running callback is waited for and rearming is blocked before the chip is halted, so it cannot fire at all once the adapter has ceased to function. Waiting outside the lock avoids the self-deadlock that would result from syncing a callback blocked on the lock we still hold.
No shutdown is needed for selto_timer because it has no reachable armer or callback.
This issue was found by an in-house static analysis tool.
Affected software and versions
| Software | Version information | Fixed version |
|---|---|---|
| LinuxLinux | affected: 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 to < 0b65c96e51e6aac86f2db251b5bdc5255294a107; affected: 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 to < a79de0e5e66bd0b69b38c855413a9e3a82926b24; affected: 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 to < bd04acf9b9d589d93823bfeeea9932cd9ce4ee48; affected: 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 to < 0b1a79f2791a06f139dce5450e487307cf0e241f | See vendor advisory |
| LinuxLinux | affected: 2.6.12; unaffected: 0 to < 2.6.12; unaffected: 6.12.117 to ≤ 6.12.*; unaffected: 6.18.61 to ≤ 6.18.*; unaffected: 7.3.2 to ≤ 7.3.*; unaffected: 7.4-rc1 to ≤ * | See vendor advisory |
Version information comes from the source record and can include unaffected products and exceptions. Distribution packages may contain backported fixes: an older upstream version alone does not prove a server is affected.
Is it being exploited?
This CVE was not listed in the CISA catalogue at our last retrieval. This does not establish that exploitation is absent.
How to respond
- Confirm the product, installed package version, and any configuration requirements in the vendor advisory.
- Follow the vendor’s remediation or workaround guidance in the references below. Structured fixed-version data is unavailable here; the publisher’s description may include a fix or workaround.
- Restart affected services if required, then verify the running version. Known exploitation may warrant investigation as well as patching.
Sources and remediation references
- https://www.cve.org/CVERecord?id=CVE-2026-99456
- https://git.kernel.org/stable/c/0b65c96e51e6aac86f2db251b5bdc5255294a107
- https://git.kernel.org/stable/c/a79de0e5e66bd0b69b38c855413a9e3a82926b24
- https://git.kernel.org/stable/c/bd04acf9b9d589d93823bfeeea9932cd9ce4ee48
- https://git.kernel.org/stable/c/0b1a79f2791a06f139dce5450e487307cf0e241f