CVE-2026-99428

Description

A flaw was found in the Linux kernel. A race condition in the OCFS2 (Oracle Cluster File System 2) file system can lead to a Denial of Service (DoS) by crashing the system or potentially result in unauthorized kernel memory disclosure. When trace events are active, a local user performing concurrent file operations, such as file renaming, can trigger a use-after-free condition where directory entry names are accessed after their memory has been released. This issue occurs because the tracing mechanism fails to safely snapshot the file name before processing it.

Statement

This vulnerability is rated as Moderate severity because an unprivileged local attacker could cause a kernel crash and system denial of service. The impact is limited because triggering the flaw requires active kernel trace events on OCFS2 operations, which are disabled by default and require administrative privileges to enable. Additionally, the issue is restricted to systems utilizing the OCFS2 filesystem and depends on winning a tight race condition between file operations and concurrent directory renames.

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 Score4.7N/AN/A
Attack VectorLocalN/AN/A
Attack ComplexityHighN/AN/A
Privileges RequiredLowN/AN/A
User InteractionNoneN/AN/A
ScopeUnchangedN/AN/A
ConfidentialityNoneN/AN/A
Integrity ImpactNoneN/AN/A
Availability ImpactHighN/AN/A

Vector

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