CVE-2025-68371: Linux kernel · scsi: smartpqi: Fix device resources accessed after device removal
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in eccc02ba1747501d92bb2049e3ce378ba372f641 : patch Linux kernel soon.
Data as of 10 Nov 2026, 13:18 UTC
Rated High by Threat Radar's AI analysis · No CVSS score from NVD or the CNA
Thin evidence
One scorer or none- Patch
- Available – fixed in eccc02ba1747501d92bb2049e3ce378ba372f641, b518e86d1a70a88f6592a7c396cf1b93493d1aab, 7dfa5a5516ec3c6b9b6c22ee18f0eb2df3f38ef2 +3
Exploitation evidence
Disclosed: evidence found.
CVE published 24 Dec 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: 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 10 Nov 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
|
AI-suggested
A fix has been implemented and is available in the Linux kernel. The fix includes checks to skip resets if the device is no longer present, cancellation of pending TMF work during device destruction, and synchronization of device freeing with a mutex. Users should update to the fixed Linux kernel versions containing these patches to remediate the issue.
Description
CVE-2025-68371 is a vulnerability in the Linux kernel's scsi smartpqi driver where device resources could be accessed after device removal due to race conditions. This could lead to use-after-free errors and improper access to freed resources. The issue arises because a scheduled work item to reset a LUN might execute after the device has been removed. The fix involves checking device presence before reset, canceling pending work during device destruction, and synchronizing device freeing with a mutex to prevent races.
References
- git.kernel.org/stable/c/7dfa5a5516ec3c6b9b6c22ee18f0eb2df3f38ef2 (opens in a new tab)
- git.kernel.org/stable/c/6d2390653d82cad0e1ba2676e536dd99678f6ef1 (opens in a new tab)
- git.kernel.org/stable/c/eccc02ba1747501d92bb2049e3ce378ba372f641 (opens in a new tab)
- git.kernel.org/stable/c/4e1acf1b6dd6dd0495bda139daafd7a403ae2dc1 (opens in a new tab)
- git.kernel.org/stable/c/1a5c5a2f88e839af5320216a02ffb075b668596a (opens in a new tab)
- git.kernel.org/stable/c/b518e86d1a70a88f6592a7c396cf1b93493d1aab (opens in a new tab)
- cert-portal.siemens.com/productcert/html/ssa-019113.html (opens in a new tab)
- cert-portal.siemens.com/productcert/html/ssa-457936.html (opens in a new tab)