| 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-37857: scsi: st: Fix array overflow in st_setup() |
| |
| Description |
| =========== |
| |
| In the Linux kernel, the following vulnerability has been resolved: |
| |
| scsi: st: Fix array overflow in st_setup() |
| |
| Change the array size to follow parms size instead of a fixed value. |
| |
| The Linux kernel CVE team has assigned CVE-2025-37857 to this issue. |
| |
| |
| Affected and fixed versions |
| =========================== |
| |
| Fixed in 5.4.293 with commit 736ae988bfb5932c05625baff70fba224d547c08 |
| Fixed in 5.10.237 with commit 574b399a7fb6ae71c97e26d122205c4a720c0e43 |
| Fixed in 5.15.181 with commit c6015d0f7a2236ddb3928b2dfcb1c556a1368b55 |
| Fixed in 6.1.135 with commit f746fe0c51e044d1248dc67918328bfb3d86b639 |
| Fixed in 6.6.88 with commit e4d1ca0a84a6650d3172eb8c07ef2fbc585b0d96 |
| Fixed in 6.12.24 with commit 7fe3b4deed8b93609058c37c9a11df1d2b2c0423 |
| Fixed in 6.13.12 with commit e6b585d016c47ca8a37b92ea8a3fe35c0b585256 |
| Fixed in 6.14.3 with commit ad4c3037dc77739a625246a2a0fb23b8f3402c06 |
| Fixed in 6.15 with commit a018d1cf990d0c339fe0e29b762ea5dc10567d67 |
| |
| 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-37857 |
| 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/st.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/736ae988bfb5932c05625baff70fba224d547c08 |
| https://git.kernel.org/stable/c/574b399a7fb6ae71c97e26d122205c4a720c0e43 |
| https://git.kernel.org/stable/c/c6015d0f7a2236ddb3928b2dfcb1c556a1368b55 |
| https://git.kernel.org/stable/c/f746fe0c51e044d1248dc67918328bfb3d86b639 |
| https://git.kernel.org/stable/c/e4d1ca0a84a6650d3172eb8c07ef2fbc585b0d96 |
| https://git.kernel.org/stable/c/7fe3b4deed8b93609058c37c9a11df1d2b2c0423 |
| https://git.kernel.org/stable/c/e6b585d016c47ca8a37b92ea8a3fe35c0b585256 |
| https://git.kernel.org/stable/c/ad4c3037dc77739a625246a2a0fb23b8f3402c06 |
| https://git.kernel.org/stable/c/a018d1cf990d0c339fe0e29b762ea5dc10567d67 |
