CVE-2024-43816

Description

A flaw was found in the Linux kernel. Specifically, within the lpfc SCSI driver, an issue exists in the lpfc_prep_embed_io routine. On big-endian architectures, incorrect handling of data endianness during a memory copy operation can lead to an out-of-bounds pointer dereference. This vulnerability can be triggered when Fibre Channel Protocol (FCP) targets are zoned, potentially causing the system to crash and resulting in a Denial of Service (DoS).

Mitigation

To mitigate this issue, prevent the `lpfc` kernel module from loading if Fibre Channel functionality provided by Emulex LightPulse Fibre Channel adapters is not required on big-endian systems.
1. Create `/etc/modprobe.d/blacklist-lpfc.conf` with `blacklist lpfc`.
2. Regenerate the initramfs using `dracut -f -v` or `mkinitrd -f -v /boot/initramfs-$(uname -r).img $(uname -r)`.
3. A system reboot is required for the changes to take effect.
This action will disable Fibre Channel functionality provided by the `lpfc` driver.

Common Vulnerability Scoring System (CVSS) Score Details

Info alert:Important note

CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authority (CNA) source for its products and services (see Red Hat classifications).

The following CVSS metrics and score provided are preliminary and subject to review.

CVSS v3 Score Breakdown

Red HatNVDcve.org
Base Score65.57.8
Attack VectorLocalLocalLocal
Attack ComplexityLowLowLow
Privileges RequiredHighLowLow
User InteractionNoneNoneNone
ScopeUnchangedUnchangedUnchanged
ConfidentialityHighNoneHigh
Integrity ImpactNoneNoneHigh
Availability ImpactHighHighHigh

Vector

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

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

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

Understanding the Weakness (CWE)

Confidentiality

Technical Impact: Read Memory

An attacker could get secret values such as cryptographic keys, PII, memory addresses, or other information that could be used in additional attacks.

Confidentiality

Technical Impact: Bypass Protection Mechanism

Out-of-bounds memory could contain memory addresses or other information that can be used to bypass ASLR and other protection mechanisms in order to improve the reliability of exploiting a separate weakness for code execution.

Availability

Technical Impact: DoS: Crash, Exit, or Restart

An attacker could cause a segmentation fault or crash by causing memory to be read outside of the bounds of the buffer. This is especially likely when the code reads a variable amount of data and assumes that a sentinel exists to stop the read operation, such as a NUL in a string.

Other

Technical Impact: Varies by Context

The read operation could produce other undefined or unexpected results.

Frequently Asked Questions

Want to get errata notifications? Sign up here.