CVE-2024-57792

Description

A flaw was found in the Linux kernel's GPIO charger driver. An out-of-bounds memory access occurs when setting a charge current limit below the minimum supported threshold on devices configured with a non-zero lowest limit. A local user could exploit this vulnerability to cause a system crash and Denial of Service (DoS) or potentially access adjacent kernel memory.

Statement

Red Hat Enterprise Linux and OpenShift are not affected by this vulnerability because the GPIO charger driver is not enabled in supported enterprise kernel builds. The issue presents minimal operational risk to enterprise deployments, as it specifically targets specialized embedded hardware with GPIO-managed battery charging controllers. An out-of-bounds memory access could only be triggered locally on platforms configured with these specific power management devices.

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.