Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2024-26917scsi: 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.

Timeline

  1. ID reserved

    By Linux

  2. · 58 days later

    Published

  3. · 2 years later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2024-26917, by who scored it
Scored byCVSSScoreVector
NVDNVD · Analyzed3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.24% · top 85% of all CVEs (17 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.

Affected products

  • Linux · Linux

    • affected 264eae2f523d2aae38188facb4ece893023f25da – < 94a600226b6d0ef065ee84024b450b566c5a87d6
    • affected d2bf25674cea74b865d367d09be5dfe9aff5922a – < 2209fc6e3d7727d787dc6ef9baa1e9eae6b1295b
    • affected 9cce8ef7a6fa858bbcacd8679a5ca5a4fd3a6df3 – < 7d4e19f7ff644c5b79e8271df8ac2e549b436a5b
    • affected 076fb40cf27ab9232d8cce1f007e663e46705302 – < 5b8f473c4de95c056c1c767b1ad48c191544f6a5
    • affected 5a5fb3b1754fa2b4db95f0151b4af0fb6f8918ec – < 6bb22ac1d11d7d20f91e7fd2e657a9e5f6db65e0
    • affected 1a1975551943f681772720f639ff42fbaa746212 – < 2996c7e97ea7cf4c1838a1b1dbc0885934113783
    • affected 1a1975551943f681772720f639ff42fbaa746212 – < 25675159040bffc7992d5163f3f33ba7d0142f21
    • affected 1a1975551943f681772720f639ff42fbaa746212 – < 977fe773dcc7098d8eaf4ee6382cb51e13e784cb
    • affected 4ea46b479a00dd232f0dbc81fdc27f9330ecb3ad
    • affected 694ddc5bf35a5b6f9acb6e4724324c910a1237f1
    • affected 6c5d7242bcf2154e9576e5eb2a98c6984ca5ea9a
    • affected 4.19.295 – < 4.19.307
    • affected 5.4.257 – < 5.4.269
    • affected 5.10.195 – < 5.10.210
    • affected 5.15.132 – < 5.15.149
    • affected 6.1.53 – < 6.1.79
    • affected 4.14.326 – < 4.15
    • affected 6.4.16 – < 6.5
    • affected 6.5.3 – < 6.6
  • Linux · Linux

    • affected 6.6
    • unaffected < 6.6
    • unaffected 4.19.307 – ≤ 4.19.*
    • unaffected 5.4.269 – ≤ 5.4.*
    • unaffected 5.10.210 – ≤ 5.10.*
    • unaffected 5.15.149 – ≤ 5.15.*
    • unaffected 6.1.79 – ≤ 6.1.*
    • unaffected 6.6.18 – ≤ 6.6.*
    • unaffected 6.7.6 – ≤ 6.7.*
    • unaffected 6.8 – ≤ *

References

References10

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2024-26917 badge
[![CVE-2024-26917](https://cveledger.app/badge/CVE-2024-26917.svg)](https://cveledger.app/cve/CVE-2024-26917)

Record last updated .