CVE-2025-68337

Description

A flaw was found in the Linux kernel's JBD2 (Journaling Block Device) subsystem. A local attacker can cause a Denial of Service (DoS) by mounting a specially crafted, corrupted file system image or triggering operations on inconsistent storage. When unexpected file system inconsistencies are encountered during file system operations, the kernel triggers an internal assertion failure instead of gracefully aborting the journal transaction, resulting in a system crash.

Statement

This vulnerability is rated as Moderate because exploiting it requires mounting a specifically crafted or corrupted ext4 filesystem image or encountering storage corruption under specific mount options, limiting the attack surface to local users with mount privileges or access to affected file operations. Successful exploitation results in a kernel panic and subsequent denial of service, but does not allow data exfiltration or privilege escalation. In standard Red Hat Enterprise Linux environments, unprivileged users cannot mount arbitrary filesystem images by default.

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.5N/A7.5
Attack VectorLocalN/ANetwork
Attack ComplexityLowN/ALow
Privileges RequiredLowN/ANone
User InteractionNoneN/ANone
ScopeUnchangedN/AUnchanged
ConfidentialityNoneN/ANone
Integrity ImpactNoneN/ANone
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:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Understanding the Weakness (CWE)

Availability

Technical Impact: DoS: Resource Consumption (Memory); DoS: Resource Consumption (Other)

If an adversary can prevent a reference count from reaching zero, then resources might not be released when they are supposed to, thus causing resources to become scarce for future needs.

Availability

Technical Impact: DoS: Crash, Exit, or Restart

If an adversary can cause a reference count to reach zero when the resource is still in use, then a resource might be released before it is supposed to be, possibly forcing an error that causes the product to crash or exit out of its current operation.

Frequently Asked Questions

Want to get errata notifications? Sign up here.