linux-cve-announce - CVE-2025-37981: scsi: smartpqi: Use is_kdump

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <2025052040-CVE-2025-37981-c41e@gregkh>
Date: Tue, 20 May 2025 18:56:45 +0200
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...nel.org>
Subject: CVE-2025-37981: scsi: smartpqi: Use is_kdump_kernel() to check for kdump

From: Greg Kroah-Hartman <gregkh@...nel.org>

Description
===========

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.

The Linux kernel CVE team has assigned CVE-2025-37981 to this issue.


Affected and fixed versions
===========================

	Issue introduced in 6.12 with commit 058311b72f54890de824b063feb603942269b732 and fixed in 6.12.25 with commit 7cc670e8ebaa5241dd99c0ad75eceb8f8f64f607
	Issue introduced in 6.12 with commit 058311b72f54890de824b063feb603942269b732 and fixed in 6.14.4 with commit ebf673c76ce91e612a882dfaa9a3824962994aae
	Issue introduced in 6.12 with commit 058311b72f54890de824b063feb603942269b732 and fixed in 6.15-rc3 with commit a2d5a0072235a69749ceb04c1a26dc75df66a31a

Please see https://www.kernel.org for a full list of currently supported
kernel versions by the kernel community.

Unaffected versions might change over time as fixes are backported to
older supported kernel versions.  The official CVE entry at
	https://cve.org/CVERecord/?id=CVE-2025-37981
will be updated if fixes are backported, please check that for the most
up to date information about this issue.


Affected files
==============

The file(s) affected by this issue are:
	drivers/scsi/smartpqi/smartpqi_init.c


Mitigation
==========

The Linux kernel CVE team recommends that you update to the latest
stable kernel version for this, and many other bugfixes.  Individual
changes are never tested alone, but rather are part of a larger kernel
release.  Cherry-picking individual commits is not recommended or
supported by the Linux kernel community at all.  If however, updating to
the latest release is impossible, the individual changes to resolve this
issue can be found at these commits:
	https://git.kernel.org/stable/c/7cc670e8ebaa5241dd99c0ad75eceb8f8f64f607
	https://git.kernel.org/stable/c/ebf673c76ce91e612a882dfaa9a3824962994aae
	https://git.kernel.org/stable/c/a2d5a0072235a69749ceb04c1a26dc75df66a31a