Answer in brief
CVE-2025-37981 records a High severity (CVSS 7.8) vulnerability in scsi: smartpqi: Use is_kdump_kernel() to check for kdump. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 7.8. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Product | Affected versions | Fixed versions |
|---|---|---|
| cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:6.15:rc1:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:6.15:rc2:*:*:*:*:*:* | Not reported | Not reported |
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=058311b72f54890de824b063feb603942269b732 <7cc670e8ebaa5241dd99c0ad75eceb8f8f64f607 || >=058311b72f54890de824b063feb603942269b732 <ebf673c76ce91e612a882dfaa9a3824962994aae || >=058311b72f54890de824b063feb603942269b732 <a2d5a0072235a69749ceb04c1a26dc75df66a31a | 7cc670e8ebaa5241dd99c0ad75eceb8f8f64f607, ebf673c76ce91e612a882dfaa9a3824962994aae, a2d5a0072235a69749ceb04c1a26dc75df66a31a |
| Linux/Linuxgeneric | 6.12 | Not reported |
Published upstream
May 20, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Nov 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Nov 5, 2026
In the Linux kernel, the following vulnerability has been resolved: scsi: smartpqi: Use is_kdump_kernel() to check for kdump The smartpqi driver checks the reset_devices variable to determine whether special adjustments need to be made for kdump. This has the effect that after a regular kexec reboot, some driver parameters such as max_transfer_size are much lower than usual. More importantly, kexec reboot tests have revealed memory corruption caused by the driver log being written to system memory after a kexec. Fix this by testing is_kdump_kernel() rather than reset_devices where appropriate.
Quoted source text, attributed separately from HOL analysis.