CVE-2025-38697

Description

A flaw was found in the Linux kernel's JFS (Journaled File System) driver. Missing boundary checks when computing metadata tree indices during block allocation can lead to an out-of-bounds memory access. A local user with privileges to mount storage volumes could exploit this vulnerability by mounting a specially crafted or corrupted filesystem image, causing a system crash and resulting in a Denial of Service (DoS).

Statement

This vulnerability is rated as Moderate because triggering the out-of-bounds access requires mounting a specially crafted or corrupted JFS filesystem image, restricting exploitation to local environments with mounting privileges. In standard Red Hat Enterprise Linux deployments, non-privileged users cannot mount arbitrary storage volumes or filesystem images without administrative intervention. Furthermore, the legacy JFS filesystem is not enabled or supported on contemporary Red Hat Enterprise Linux releases, significantly constraining the overall blast radius.

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.87.87.8
Attack VectorLocalLocalLocal
Attack ComplexityHighLowLow
Privileges RequiredLowLowLow
User InteractionNoneNoneNone
ScopeUnchangedUnchangedUnchanged
ConfidentialityLowHighHigh
Integrity ImpactLowHighHigh
Availability ImpactHighHighHigh

Vector

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

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.