CVE-2024-26917

scsi: Revert "scsi: fcoe: Fix potential deadlock on &fip->ctlr_lock"

MEDIUM

5.5

CVSS Score

Published: April 17, 2024 at 03:59 PM UTC

Updated: June 17, 2026 at 07:18 AM UTC

2 products affected across 2 vendorsLinux KernelDebian Linux

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available

Start Free Sign In

Severity

MEDIUM5.5

Exploit prediction

EPSS 0.2%

SSVC

No known exploit

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

Debian Linux · Debiandrupal

95%

10.0

Linux Kernel · Linux

95%

v ≥ 4.14.326v ≥ 6.4.16v ≥ 6.5.34.14.326 ≤ v < 4.154.19.295 ≤ v < 4.19.3075.10.195 ≤ v < 5.10.2105.15.132 ≤ v < 5.15.1495.4.257 ≤ v < 5.4.2696.1.53 ≤ v < 6.1.796.4.16 ≤ v < 6.56.5.3 ≤ v < 6.66.5.3 ≤ v < 6.6.186.6 ≤ v < 6.6.186.6 ≤ v < 6.7.66.6 ≤ v < 6.86.7 ≤ v < 6.7.61a1975551943f681772720f639ff42fbaa746212264eae2f523d2aae38188facb4ece893023f25da4.14.326 4.19.2954ea46b479a00dd232f0dbc81fdc27f9330ecb3ad5.10.195 5.15.132 5.4.2575a5fb3b1754fa2b4db95f0151b4af0fb6f8918ec6.1.53 6.4.16 6.5.3 6.8 rc1 6.8 rc2 6.8 rc3 6.8 rc4694ddc5bf35a5b6f9acb6e4724324c910a1237f16c5d7242bcf2154e9576e5eb2a98c6984ca5ea9a76fb40cf27ab9232d8cce1f7e663e467053029cce8ef7a6fa858bbcacd8679a5ca5a4fd3a6df3d2bf25674cea74b865d367d09be5dfe9aff5922a

Vendor states this is fixed in 2209fc6e3d7727d787dc6ef9baa1e9eae6b1295b (fixed)

Vendor states this is fixed in 25675159040bffc7992d5163f3f33ba7d0142f21 (fixed)

Vendor states this is fixed in 2996c7e97ea7cf4c1838a1b1dbc0885934113783 (fixed)

Vendor states this is fixed in 5b8f473c4de95c056c1c767b1ad48c191544f6a5 (fixed)

Vendor states this is fixed in 6bb22ac1d11d7d20f91e7fd2e657a9e5f6db65e0 (fixed)

Vendor states this is fixed in 7d4e19f7ff644c5b79e8271df8ac2e549b436a5b (fixed)

Vendor states this is fixed in 94a600226b6d0ef065ee84024b450b566c5a87d6 (fixed)

Vendor states this is fixed in 977fe773dcc7098d8eaf4ee6382cb51e13e784cb (fixed)

Affected range stops below 4.15, so it looks safe — our inference, not a vendor statement

Vendor states this is fixed in 4.19.307 (unaffected)

Vendor states this is fixed in 5.10.210 (unaffected)

Vendor states this is fixed in 5.15.149 (unaffected)

Vendor states this is fixed in 5.4.269 (unaffected)

Vendor states this is fixed in 6.1.79 (unaffected)

Affected range stops below 6.5, so it looks safe — our inference, not a vendor statement

Vendor states this is fixed in 6.6 (unaffected)

Vendor states this is fixed in 6.6.18 (unaffected)

Vendor states this is fixed in 6.7.6 (unaffected)

Vendor states this is fixed in 6.8 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

Patch and advisory references