scsi: smartpqi: Use is_kdump_kernel() to check for kdump
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
6.12.256.14.46.15In 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.
From the CVE record · Linux
The Linux kernel smartpqi driver uses an incorrect check for kdump, causing some driver parameters to be lower than usual after a regular kexec reboot. Kexec reboot tests also revealed memory corruption when the driver log was written to system memory after kexec. The input does not describe an attacker path, authentication requirement, or user interaction.
Engineers running Linux kernels with the smartpqi driver should check their versions; the affected versions are not specified.