CVE-2023-54135

Description

From CVE.org

In the Linux kernel, the following vulnerability has been resolved: maple_tree: fix potential out-of-bounds access in mas_wr_end_piv() Check the write offset end bounds before using it as the offset into the pivot array. This avoids a possible out-of-bounds access on the pivot array if the write extends to the last slot in the node, in which case the node maximum should be used as the end pivot. akpm: this doesn't affect any current callers, but new users of mapletree may encounter this problem if backported into earlier kernels, so let's fix it in -stable kernels in case of this.

Statement

A low impact out-of-bounds access was found in the Linux kernel's maple tree implementation (lib/maple_tree.c). In mas_wr_end_piv(), the write offset end was used as an index into the pivot array without first checking its bounds, which can cause an out-of-bounds access on the pivot array when a write extends to the last slot in a node; in that case the node maximum should be used as the end pivot. Red Hat rated this flaw Low impact (CVSS 3.1 score 5.5, AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H) because it requires local access and the expected impact is limited to kernel availability, whereas the upstream CVE.org record assigns a higher score (7.8) by assuming confidentiality and integrity impacts that Red Hat's assessment does not support. Upstream further noted that no current callers reach the problematic path; the issue only arises for new users of the maple tree or when the code is backported to earlier kernels, which limits practical exposure. The vulnerable code is not present in Red Hat Enterprise Linux 6, 7, 8, and 10 or in Red Hat In-Vehicle OS, so those products are not affected; only the Red Hat Enterprise Linux 9 kernel and kernel-rt contain the vulnerable code. The fix for the affected Red Hat Enterprise Linux 9 streams is deferred given the low practical impact of this flaw, leaving a residual risk that a local user could trigger the out-of-bounds access in the maple tree code and crash the kernel (denial of service) if a code path exercising the flawed bounds handling is reached.

Mitigation

Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.

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).

CVSS v3 Score Breakdown

Red HatNVDcve.org
Base Score5.5N/A7.8
Attack VectorLocalN/ALocal
Attack ComplexityLowN/ALow
Privileges RequiredLowN/ALow
User InteractionNoneN/ANone
ScopeUnchangedN/AUnchanged
ConfidentialityNoneN/AHigh
Integrity ImpactNoneN/AHigh
Availability ImpactHighN/AHigh

Vector

Red Hat: 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)

Integrity

Technical Impact: Modify Memory; Execute Unauthorized Code or Commands

Write operations could cause memory corruption. In some cases, an adversary can modify control data such as return addresses in order to execute unexpected code.

Availability

Technical Impact: DoS: Crash, Exit, or Restart

Attempting to access out-of-range, invalid, or unauthorized memory could cause the product to crash.

Other

Technical Impact: Unexpected State

Subsequent write operations can produce undefined or unexpected results.

Frequently Asked Questions

Want to get errata notifications? Sign up here.