CVE-2026-99693

Description

A flaw was found in the Linux kernel's Oracle Cluster File System 2 (OCFS2) distributed lock manager (DLM). This vulnerability can result in a Denial of Service (DoS) due to a use-after-free condition. When lock resource migration encounters a network error or node disconnect, improper reference counting causes memory to be prematurely released. A local user or cluster event triggering this failure path causes the kernel to access the freed memory, leading to a system crash.

Statement

This flaw is rated as Moderate impact for Red Hat enterprise environments because triggering the condition requires an active cluster configuration using the OCFS2 file system and specific race or network failure conditions, limiting the potential blast radius to local denial of service. In typical Red Hat Enterprise Linux deployments, the OCFS2 kernel modules are not loaded by default and require explicit administrative setup of cluster infrastructure. Consequently, unprivileged users cannot trigger the condition on standard installations, and systems that do not mount or participate in OCFS2 clusters remain unaffected.

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.1N/AN/A
Attack VectorLocalN/AN/A
Attack ComplexityHighN/AN/A
Privileges RequiredHighN/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:H/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.