LiveActive security incident?Get immediate response
CVE Record

CVE-2024-36924: scsi: lpfc: Release hbalock before calling lpfc_worker_wake_up()

In the Linux kernel, the following vulnerability has been resolved: scsi: lpfc: Release hbalock before calling lpfc_worker_wake_up() lpfc_worker_wake_up() calls the lpfc_work_done() routine, which takes the hbalock. Thus, lpfc_worker_wake_up() should not be called while holding the hbalock to avoid potential deadlock.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This Linux kernel issue can deadlock systems using the lpfc SCSI Fibre Channel driver. A deadlock can make affected storage paths or hosts hang, creating availability risk. The public record does not provide CVSS scoring, exploit details, or evidence of active exploitation.

Executive priority

Handle in the next planned kernel maintenance cycle, faster for critical Fibre Channel storage hosts. The business risk is service interruption, not confirmed data compromise, based on the available sources.

Technical view

The lpfc driver called lpfc_worker_wake_up() while holding hbalock. That worker path can enter lpfc_work_done(), which also takes hbalock, creating a potential lock-order deadlock. Stable Linux commits move the wake-up call outside the locked section.

Likely exposure

Exposure is most likely on Linux systems running affected kernel builds where the lpfc driver is present and used for Fibre Channel storage. Distro backports may change exposure, so kernel package advisories matter more than upstream version numbers alone.

Exploitation context

The source bundle does not show KEV listing, public exploitation, exploit code, or attacker prerequisites. Treat this primarily as an availability and operational stability issue unless vendor advisories add stronger exploitation evidence.

Researcher notes

Evidence is limited but technically clear: this is a resolved Linux kernel lpfc locking bug. No CWE, CVSS, or exploitation details are provided in the bundle. Validation should focus on driver presence, kernel lineage, and distro backport status.

Mitigation direction

  • Apply vendor kernel updates that include the referenced Linux stable fixes.
  • Prioritize storage hosts using the lpfc Fibre Channel driver.
  • Check Linux distribution advisories for backported fixed packages.
  • Schedule updates through normal storage change-control procedures.
  • If no vendor fix is available, request vendor guidance before applying workarounds.

Validation and detection

  • Inventory systems with Linux kernels and lpfc driver usage.
  • Compare installed kernel packages against vendor fixed versions or stable fix commits.
  • Review kernel logs for lpfc-related hangs, stalls, or deadlock symptoms.
  • Confirm updated kernels are running after maintenance windows.
  • Track this CVE in vulnerability management until vendor status is closed.
Prepared
Confidence
medium
Sources
6

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2024-36924 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
2ADP providers
5Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc
CVECVE Program Container

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux92d7f7b0cde3ad2260e7462b40867b57efd49851, 92d7f7b0cde3ad2260e7462b40867b57efd49851, 92d7f7b0cde3ad2260e7462b40867b57efd49851, 92d7f7b0cde3ad2260e7462b40867b57efd49851unaffected
LinuxLinux2.6.23, 0, 6.1.91, 6.6.31, 6.8.10, 6.9affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.