| From bippy-1.2.0 Mon Sep 17 00:00:00 2001 |
| From: Greg Kroah-Hartman <gregkh@kernel.org> |
| To: <linux-cve-announce@vger.kernel.org> |
| Reply-to: <cve@kernel.org>, <linux-kernel@vger.kernel.org> |
| Subject: CVE-2025-37861: scsi: mpi3mr: Synchronous access b/w reset and tm thread for reply queue |
| |
| Description |
| =========== |
| |
| In the Linux kernel, the following vulnerability has been resolved: |
| |
| scsi: mpi3mr: Synchronous access b/w reset and tm thread for reply queue |
| |
| When the task management thread processes reply queues while the reset |
| thread resets them, the task management thread accesses an invalid queue ID |
| (0xFFFF), set by the reset thread, which points to unallocated memory, |
| causing a crash. |
| |
| Add flag 'io_admin_reset_sync' to synchronize access between the reset, |
| I/O, and admin threads. Before a reset, the reset handler sets this flag to |
| block I/O and admin processing threads. If any thread bypasses the initial |
| check, the reset thread waits up to 10 seconds for processing to finish. If |
| the wait exceeds 10 seconds, the controller is marked as unrecoverable. |
| |
| The Linux kernel CVE team has assigned CVE-2025-37861 to this issue. |
| |
| |
| Affected and fixed versions |
| =========================== |
| |
| Issue introduced in 5.14 with commit c4f7ac64616ee513f9ac4ae6c4d8c3cccb6974df and fixed in 6.12.24 with commit 65ba18c84dbd03afe9b38c06c151239d97a09834 |
| Issue introduced in 5.14 with commit c4f7ac64616ee513f9ac4ae6c4d8c3cccb6974df and fixed in 6.13.12 with commit 8d310d66e2b0f5f9f709764641647e8a3a4924fa |
| Issue introduced in 5.14 with commit c4f7ac64616ee513f9ac4ae6c4d8c3cccb6974df and fixed in 6.14.3 with commit 75b67dca4195e11ccf966a704787b2aa2754a457 |
| Issue introduced in 5.14 with commit c4f7ac64616ee513f9ac4ae6c4d8c3cccb6974df and fixed in 6.15 with commit f195fc060c738d303a21fae146dbf85e1595fb4c |
| |
| 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-37861 |
| 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/mpi3mr/mpi3mr.h |
| drivers/scsi/mpi3mr/mpi3mr_fw.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/65ba18c84dbd03afe9b38c06c151239d97a09834 |
| https://git.kernel.org/stable/c/8d310d66e2b0f5f9f709764641647e8a3a4924fa |
| https://git.kernel.org/stable/c/75b67dca4195e11ccf966a704787b2aa2754a457 |
| https://git.kernel.org/stable/c/f195fc060c738d303a21fae146dbf85e1595fb4c |
