CVE-2024-24855: Race condition vulnerability in Linux kernel scsi device driver lpfc_unregister_fcf_rescan()
A race condition was found in the Linux kernel's scsi device driver in lpfc_unregister_fcf_rescan() function. This can result in a null pointer dereference issue, possibly leading to a kernel panic or denial of service issue.
Security readout for executives and security teams
Plain-English summary
CVE-2024-24855 is a Linux kernel race condition in the lpfc SCSI/Fibre Channel driver. Under constrained local conditions, it may trigger a null pointer dereference, causing a kernel panic or denial of service. The provided evidence does not show active exploitation.
Executive priority
Treat as a moderate infrastructure reliability issue. It is most urgent for storage-connected Linux servers where an unplanned kernel panic would disrupt critical workloads. No evidence provided supports emergency internet-wide response or active exploitation handling.
Technical view
The flaw is in lpfc_unregister_fcf_rescan() and is classified as CWE-362. CVSS 3.1 is 5.0 with local access, high attack complexity, low privileges, and user interaction required. The main impact is availability loss; integrity impact is listed as low, with no confidentiality impact.
Likely exposure
Exposure is most relevant to Linux systems using the lpfc driver, typically Fibre Channel storage environments. The source bundle lists Linux kernel v2.6.34-rc2 and references Debian LTS, OpenAnolis, and Siemens advisories. Product-specific affected ranges require vendor confirmation.
Exploitation context
This is not listed in KEV, and the provided sources do not claim exploitation in the wild. The CVSS vector indicates exploitation requires local access, low privileges, high complexity, and user interaction, which materially limits practical abuse compared with remote unauthenticated kernel flaws.
Researcher notes
The evidence is limited to a CVE record and vendor advisories. The record identifies the function and impact but does not provide exploit details or complete product version ranges. Validate exposure through driver use and vendor-specific kernel package status rather than the generic Linux label alone.
Mitigation direction
Check applicable Linux distribution and vendor advisories for fixed kernel packages.
Prioritize updates on systems using lpfc-connected Fibre Channel storage.
Restrict local shell access to trusted administrators where patching is delayed.
Follow Debian LTS, Siemens, OpenAnolis, or platform vendor guidance for remediation.
Monitor vendor advisories for clarified affected versions and backports.
Validation and detection
Inventory Linux kernel versions across servers and appliances.
Identify systems where the lpfc driver is present or loaded.
Map affected assets to Debian, Siemens, OpenAnolis, or vendor advisory scope.
Confirm kernel package update status against vendor-fixed releases.
Review crash logs for kernel panics involving lpfc paths.
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.
cwe · low confidence lookup
CWE-362: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
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.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-362 · source CWE mapping
Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')
Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.