LiveActive security incident?Get immediate response
CVE Record

CVE-2024-46842: scsi: lpfc: Handle mailbox timeouts in lpfc_get_sfp_info

In the Linux kernel, the following vulnerability has been resolved: scsi: lpfc: Handle mailbox timeouts in lpfc_get_sfp_info The MBX_TIMEOUT return code is not handled in lpfc_get_sfp_info and the routine unconditionally frees submitted mailbox commands regardless of return status. The issue is that for MBX_TIMEOUT cases, when firmware returns SFP information at a later time, that same mailbox memory region references previously freed memory in its cmpl routine. Fix by adding checks for the MBX_TIMEOUT return code. During mailbox resource cleanup, check the mbox flag to make sure that the wait did not timeout. If the MBOX_WAKE flag is not set, then do not free the resources because it will be freed when firmware completes the mailbox at a later time in its cmpl routine. Also, increase the timeout from 30 to 60 seconds to accommodate boot scripts requiring longer timeouts.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

This is a Linux kernel driver memory-safety bug in the lpfc SCSI path. If a mailbox request times out, the driver could free memory that firmware may later use when completing the request. The bundle does not provide a CVSS score or evidence of active exploitation.

Executive priority

Treat as a targeted infrastructure maintenance item, not an emergency from the available evidence. Prioritize storage servers or hosts using lpfc, and track vendor kernel updates because kernel memory-safety bugs can affect reliability and availability.

Technical view

In lpfc_get_sfp_info, MBX_TIMEOUT was not handled. The routine freed mailbox resources regardless of return status, creating a later completion path that could reference freed memory. The fix checks MBX_TIMEOUT and MBOX_WAKE before freeing resources, and increases the timeout from 30 to 60 seconds.

Likely exposure

Exposure appears limited to Linux systems running affected kernel versions with the lpfc SCSI driver path in use. The bundle lists Linux as affected but does not provide distribution-specific package names, configurations, or a complete version matrix.

Exploitation context

No active exploitation is supported by the provided sources, and the CVE is not marked KEV. The source describes a timeout-driven driver bug, but provides no exploitability assessment, impact rating, or public attack details.

Researcher notes

The core issue is lifetime handling after MBX_TIMEOUT in lpfc_get_sfp_info. Evidence supports a use-after-free style condition, but the bundle lacks CVSS, CWE, exploitability notes, and distribution mapping. Validate through source or vendor backport status.

Mitigation direction

  • Check Linux vendor or distribution advisories for fixed kernel packages.
  • Update to a kernel containing the referenced stable fixes.
  • Prioritize systems using the lpfc SCSI driver or related storage hardware.
  • Avoid inventing workarounds; follow vendor guidance if patching is delayed.

Validation and detection

  • Inventory Linux kernel versions across storage-facing hosts.
  • Confirm whether the lpfc driver is present and in use.
  • Verify installed kernels include the referenced stable commits or downstream backports.
  • Review kernel or driver logs for mailbox timeout symptoms.
Prepared
Confidence
medium
Sources
4

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-46842 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
1ADP providers
3Source 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
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux479b0917e4477f49df2e3be454aac3cfa5dec171, 479b0917e4477f49df2e3be454aac3cfa5dec171unaffected
LinuxLinux6.2, 0, 6.10.10, 6.11affected
Weakness

CWE details

No CWE listed

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