Bug 2367622 (CVE-2025-37981) - CVE-2025-37981 kernel: scsi: smartpqi: Use is_kdump_kernel() to check for kdump
Summary: CVE-2025-37981 kernel: scsi: smartpqi: Use is_kdump_kernel() to check for kdump
Keywords:
Status: NEW
Alias: CVE-2025-37981
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Product Security DevOps Team
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2025-05-20 18:02 UTC by OSIDB Bzimport
Modified: 2025-06-11 17:45 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

Description OSIDB Bzimport 2025-05-20 18:02:19 UTC
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.

Comment 1 Avinash Hanwate 2025-05-21 04:17:11 UTC
Upstream advisory:
https://lore.kernel.org/linux-cve-announce/2025052040-CVE-2025-37981-c41e@gregkh/T


Note You need to log in before you can comment on or make changes to this bug.