LiveActive security incident?Get immediate response
CVE Record

CVE-2024-43816: scsi: lpfc: Revise lpfc_prep_embed_io routine with proper endian macro usages

In the Linux kernel, the following vulnerability has been resolved: scsi: lpfc: Revise lpfc_prep_embed_io routine with proper endian macro usages On big endian architectures, it is possible to run into a memory out of bounds pointer dereference when FCP targets are zoned. In lpfc_prep_embed_io, the memcpy(ptr, fcp_cmnd, sgl->sge_len) is referencing a little endian formatted sgl->sge_len value. So, the memcpy can cause big endian systems to crash. Redefine the *sgl ptr as a struct sli4_sge_le to make it clear that we are referring to a little endian formatted data structure. And, update the routine with proper le32_to_cpu macro usages.

HighCVSS 7.8Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

A Linux Fibre Channel driver flaw can crash certain big-endian systems when FCP targets are zoned. The vulnerable code misreads a data length because of byte-order handling, potentially accessing memory outside valid bounds. Exposure is specialized, but affected storage servers could suffer serious disruption.

Executive priority

Treat this as a high-priority, narrowly scoped infrastructure issue. Rapidly identify big-endian lpfc storage hosts, especially systems supporting critical workloads, and patch confirmed exposures. Broad emergency action across ordinary little-endian Linux fleets is not supported by the supplied evidence.

Technical view

The lpfc driver’s lpfc_prep_embed_io routine used little-endian sgl->sge_len directly as a memcpy length. On big-endian architectures, the misinterpreted value can cause an out-of-bounds pointer dereference. The referenced correction uses the little-endian SGE structure explicitly and converts relevant values with le32_to_cpu.

Likely exposure

Exposure requires a vulnerable Linux kernel, big-endian architecture, the lpfc Fibre Channel driver, and zoned FCP targets. The bundle indicates affected 6.10-series versions but does not clearly establish every distribution-specific package. Typical little-endian Linux systems are outside the described failure condition.

Exploitation context

The CVSS vector describes a local, low-complexity attack requiring low privileges and no user interaction. The supplied sources do not establish active exploitation, and this CVE is not identified as KEV. The published technical description specifically documents system crashes; broader confidentiality or integrity consequences are not demonstrated.

Researcher notes

The root cause is an endian mismatch in an SGE length consumed by memcpy. Assessment should focus on architecture, lpfc reachability, zoning state, and exact backport status. Avoid inferring remote exploitability or proven code execution: neither is established by the supplied record.

Mitigation direction

  • Apply a vendor-supported kernel containing the referenced lpfc endian-handling correction.
  • Prioritize affected big-endian Fibre Channel storage systems and other availability-critical hosts.
  • Consult the Linux distribution advisory to confirm its fixed package version.
  • Restrict unnecessary local access while remediation remains pending.

Validation and detection

  • Inventory big-endian Linux hosts and record their exact kernel package versions.
  • Determine whether the lpfc driver is loaded and actively managing Fibre Channel storage.
  • Confirm whether connected FCP targets use the relevant zoning configuration.
  • Verify the installed kernel includes a referenced fix or vendor-confirmed backport.
  • Review kernel logs for lpfc-related crashes or invalid memory access events.
Prepared
Confidence
medium
Sources
4

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-43816 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
High
CVSS
7.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

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.

1CVSS vectors
3Timeline events
1ADP providers
3Source links

SSVC decision data

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

CVSS vector scores

1 official score

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.

ScoreVersionSeverityVectorExploitImpactSource
7.8CVSS 3.1HighCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H1.85.9Linux

Vulnerability scoring details

Base CVSS 3.1 score

7.8High
CVSS 3.1 vector shape for CVE-2024-43816Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

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

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxaf20bb73ac2591631d504f3f859f073bcdb7e11e, af20bb73ac2591631d504f3f859f073bcdb7e11eunaffected
LinuxLinux6.10, 0, 6.10.3, 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.