CVE-2025-37981: Linux kernel · scsi: smartpqi: Use is_kdump_kernel() to check for kdump
Affects Linux kernelSource GCVE Database
Not known to be exploited.
Data as of 5 Nov 2026, 21:51 UTC
Rated High by Threat Radar's AI analysis · No CVSS score from NVD or the CNA
Thin evidence
One scorer or noneExploitation evidence
Disclosed: evidence found.
CVE published 20 May 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 5 Nov 2026.
What to do
AI-suggested
A fix has been implemented in the Linux kernel to address this issue by using is_kdump_kernel() instead of reset_devices for kdump detection in the smartpqi driver. Users should update to the fixed kernel version once available.
Description
A vulnerability in the Linux kernel's smartpqi SCSI driver was fixed by changing the method used to detect kdump kernel mode. Previously, the driver used the reset_devices variable, which caused improper parameter settings and memory corruption after kexec reboots. The fix involves using the is_kdump_kernel() function to correctly identify kdump mode and prevent these issues.