CVE-2024-44973

Description

A flaw was found in the Linux kernel's SLUB memory management subsystem. When releasing batches of memory objects, the kernel fails to verify whether an object is managed by the Kernel Electric-Fence (KFENCE) memory safety mechanism. A local user can trigger this condition through operations that invoke bulk memory freeing routines, causing memory corruption and a kernel crash that results in a denial of service (DoS).

Statement

This vulnerability is rated as Moderate severity because exploitation requires local system access and is restricted to causing a kernel crash and denial of service, with no compromise to system confidentiality or integrity. The flawed memory-freeing logic was introduced in upstream kernel versions that are newer than those provided in supported releases such as Red Hat Enterprise Linux 8 and 9, which remain unaffected. For environments running affected upstream kernels, standard unprivileged local interactions with subsystems invoking bulk object free routines could trigger this slab corruption.

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 Score5.55.58.1
Attack VectorLocalLocalNetwork
Attack ComplexityLowLowHigh
Privileges RequiredLowLowNone
User InteractionNoneNoneNone
ScopeUnchangedUnchangedUnchanged
ConfidentialityNoneNoneHigh
Integrity ImpactNoneNoneHigh
Availability ImpactHighHighHigh

Vector

Red Hat: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/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:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

Understanding the Weakness (CWE)

Availability

Technical Impact: DoS: Crash, Exit, or Restart; DoS: Resource Consumption (CPU); DoS: Resource Consumption (Memory)

An attacker could provide unexpected values and cause a program crash or arbitrary control of resource allocation, leading to excessive consumption of resources such as memory and CPU.

Confidentiality

Technical Impact: Read Memory; Read Files or Directories

An attacker could read confidential data if they are able to control resource references.

Integrity,Confidentiality,Availability

Technical Impact: Modify Memory; Execute Unauthorized Code or Commands

An attacker could use malicious input to modify data or possibly alter control flow in unexpected ways, including arbitrary command execution.

Frequently Asked Questions

Want to get errata notifications? Sign up here.