blob: 66cc0d827f6ede2fc152915a0d2d5485c0549b98 [file] [log] [blame]
From bippy-5f407fcff5a0 Mon Sep 17 00:00:00 2001
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: <linux-cve-announce@vger.kernel.org>
Reply-to: <cve@kernel.org>, <linux-kernel@vger.kernel.org>
Subject: CVE-2024-26917: scsi: Revert "scsi: fcoe: Fix potential deadlock on &fip->ctlr_lock"
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
scsi: Revert "scsi: fcoe: Fix potential deadlock on &fip->ctlr_lock"
This reverts commit 1a1975551943f681772720f639ff42fbaa746212.
This commit causes interrupts to be lost for FCoE devices, since it changed
sping locks from "bh" to "irqsave".
Instead, a work queue should be used, and will be addressed in a separate
commit.
The Linux kernel CVE team has assigned CVE-2024-26917 to this issue.
Affected and fixed versions
===========================
Issue introduced in 4.19.295 with commit 264eae2f523d2aae38188facb4ece893023f25da and fixed in 4.19.307 with commit 94a600226b6d0ef065ee84024b450b566c5a87d6
Issue introduced in 5.4.257 with commit d2bf25674cea74b865d367d09be5dfe9aff5922a and fixed in 5.4.269 with commit 2209fc6e3d7727d787dc6ef9baa1e9eae6b1295b
Issue introduced in 5.10.195 with commit 9cce8ef7a6fa858bbcacd8679a5ca5a4fd3a6df3 and fixed in 5.10.210 with commit 7d4e19f7ff644c5b79e8271df8ac2e549b436a5b
Issue introduced in 5.15.132 with commit 076fb40cf27ab9232d8cce1f007e663e46705302 and fixed in 5.15.149 with commit 5b8f473c4de95c056c1c767b1ad48c191544f6a5
Issue introduced in 6.1.53 with commit 5a5fb3b1754fa2b4db95f0151b4af0fb6f8918ec and fixed in 6.1.79 with commit 6bb22ac1d11d7d20f91e7fd2e657a9e5f6db65e0
Issue introduced in 6.6 with commit 1a1975551943f681772720f639ff42fbaa746212 and fixed in 6.6.18 with commit 2996c7e97ea7cf4c1838a1b1dbc0885934113783
Issue introduced in 6.6 with commit 1a1975551943f681772720f639ff42fbaa746212 and fixed in 6.7.6 with commit 25675159040bffc7992d5163f3f33ba7d0142f21
Issue introduced in 6.6 with commit 1a1975551943f681772720f639ff42fbaa746212 and fixed in 6.8 with commit 977fe773dcc7098d8eaf4ee6382cb51e13e784cb
Issue introduced in 4.14.326 with commit 4ea46b479a00dd232f0dbc81fdc27f9330ecb3ad
Issue introduced in 6.4.16 with commit 694ddc5bf35a5b6f9acb6e4724324c910a1237f1
Issue introduced in 6.5.3 with commit 6c5d7242bcf2154e9576e5eb2a98c6984ca5ea9a
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-2024-26917
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/fcoe/fcoe_ctlr.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/94a600226b6d0ef065ee84024b450b566c5a87d6
https://git.kernel.org/stable/c/2209fc6e3d7727d787dc6ef9baa1e9eae6b1295b
https://git.kernel.org/stable/c/7d4e19f7ff644c5b79e8271df8ac2e549b436a5b
https://git.kernel.org/stable/c/5b8f473c4de95c056c1c767b1ad48c191544f6a5
https://git.kernel.org/stable/c/6bb22ac1d11d7d20f91e7fd2e657a9e5f6db65e0
https://git.kernel.org/stable/c/2996c7e97ea7cf4c1838a1b1dbc0885934113783
https://git.kernel.org/stable/c/25675159040bffc7992d5163f3f33ba7d0142f21
https://git.kernel.org/stable/c/977fe773dcc7098d8eaf4ee6382cb51e13e784cb