LiveActive security incident?Get immediate response
CVE Record

CVE-2024-35930: scsi: lpfc: Fix possible memory leak in lpfc_rcv_padisc()

In the Linux kernel, the following vulnerability has been resolved: scsi: lpfc: Fix possible memory leak in lpfc_rcv_padisc() The call to lpfc_sli4_resume_rpi() in lpfc_rcv_padisc() may return an unsuccessful status. In such cases, the elsiocb is not issued, the completion is not called, and thus the elsiocb resource is leaked. Check return value after calling lpfc_sli4_resume_rpi() and conditionally release the elsiocb resource.

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

Security readout for executives and security teams

Plain-English summary

CVE-2024-35930 is a Linux kernel memory leak in the SCSI lpfc code. When an internal resume operation fails, a resource may not be freed. The source bundle does not show code execution or data exposure. The main concern is resource exhaustion or instability on systems running affected kernels where this driver path is used.

Executive priority

Handle through normal kernel patch governance, with higher priority for production systems using lpfc-backed storage. There is no cited active exploitation, but kernel resource leaks can affect availability, so do not leave exposed systems outside routine patch cycles.

Technical view

In lpfc_rcv_padisc(), lpfc_sli4_resume_rpi() can return an unsuccessful status. Before the fix, that path could leave elsiocb unissued and without completion handling, leaking the elsiocb resource. Kernel stable commits add return-value handling and conditional resource release. No CVSS, CWE, or attacker prerequisites are provided.

Likely exposure

Exposure is most likely limited to Linux systems on affected kernel versions that use the SCSI lpfc driver path. The bundle lists Linux kernel versions including 3.4 through 6.9 as affected and multiple stable commit references as fixes, but does not identify specific distributions beyond Debian LTS advisories.

Exploitation context

The bundle does not report active exploitation, public exploit availability, or KEV listing. It describes a kernel memory leak triggered by an unsuccessful internal driver operation. Without more evidence, treat exploitation conditions and external reachability as unknown.

Researcher notes

Evidence is narrow: the CVE text and stable commit references describe a missed cleanup path, not exploitability. Useful follow-up is version-to-fix mapping for each distribution kernel and determining whether lpfc_rcv_padisc() is reachable in deployed storage configurations.

Mitigation direction

  • Update affected Linux kernels to versions containing the referenced stable fixes.
  • Review Debian LTS advisories if running Debian-based systems.
  • Check Siemens guidance if using affected Siemens products or platforms.
  • Prioritize systems using the SCSI lpfc driver in production storage paths.
  • If patch timing is unclear, follow vendor kernel guidance.

Validation and detection

  • Inventory Linux kernel versions across servers and appliances.
  • Check whether the lpfc driver is present or in use.
  • Map installed kernel builds to vendor advisories or stable fix commits.
  • Confirm Debian LTS package status where applicable.
  • Monitor kernel logs for driver errors or resource pressure.
Prepared
Confidence
medium
Sources
12

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-35930 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
3ADP providers
12Source 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
siemens-SADPADP container

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux6b5151fd7baec6812fece993ddd7a2cf9fd0125f, 6b5151fd7baec6812fece993ddd7a2cf9fd0125f, 6b5151fd7baec6812fece993ddd7a2cf9fd0125f, 6b5151fd7baec6812fece993ddd7a2cf9fd0125f, 6b5151fd7baec6812fece993ddd7a2cf9fd0125f, 6b5151fd7baec6812fece993ddd7a2cf9fd0125f, 6b5151fd7baec6812fece993ddd7a2cf9fd0125f, 6b5151fd7baec6812fece993ddd7a2cf9fd0125funaffected
LinuxLinux3.4, 0, 4.19.312, 5.4.274, 5.10.215, 5.15.155, 6.1.86, 6.6.27, 6.8.6, 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.