CVE-2024-49883

Description

A flaw was found in the Linux kernel's ext4 filesystem driver. When modifying filesystem structures during extent allocation, the kernel fails to update an internal path reference after reallocation, resulting in a use-after-free vulnerability where memory is accessed after being deallocated. A local user with write privileges on an ext4 filesystem can exploit this issue during writeback or block mapping operations to cause a Denial of Service (DoS) by crashing the kernel, or potentially corrupt system memory.

Statement

This vulnerability is rated as Moderate because exploitation requires a local user to have write privileges on an ext4 filesystem, with the resulting impact primarily limited to a kernel crash and denial of service. While ext4 is fully supported across Red Hat Enterprise Linux releases, standard installations deploy XFS by default, restricting potential exposure to systems actively utilizing ext4 storage volumes. Exploitation relies on specific extent tree reallocation conditions during block mapping and writeback, preventing remote or unprivileged triggering on default configurations without ext4 write access.

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.57.87.8
Attack VectorLocalLocalLocal
Attack ComplexityLowLowLow
Privileges RequiredLowLowLow
User InteractionNoneNoneNone
ScopeUnchangedUnchangedUnchanged
ConfidentialityNoneHighHigh
Integrity ImpactNoneHighHigh
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:H/I:H/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

If the expired pointer is used in a read operation, an attacker might be able to control data read in by the application.

Availability

Technical Impact: DoS: Crash, Exit, or Restart

If the expired pointer references a memory location that is not accessible to the product, or points to a location that is "malformed" (such as NULL) or larger than expected by a read or write operation, then a crash may occur.

Integrity,Confidentiality,Availability

Technical Impact: Execute Unauthorized Code or Commands

If the expired pointer is used in a function call, or points to unexpected data in a write operation, then code execution may be possible.

Frequently Asked Questions

Want to get errata notifications? Sign up here.