CVE-2026-99431

Description

A flaw was found in the Linux kernel's OCFS2 (Oracle Cluster File System 2) file system. When remounting a file system from read-only to read-write, quota synchronization work may remain scheduled even if quota initialization fails and the associated quota data is freed. When the delayed work timer subsequently expires, the system attempts to access the released memory, causing a use-after-free condition. A local attacker with remount privileges could exploit this vulnerability to trigger a Denial of Service (DoS) via a kernel crash or potentially corrupt system memory.

Statement

This vulnerability is rated as Moderate impact because exploitation requires local administrative privileges (such as CAP_SYS_ADMIN) to perform a filesystem remount, restricting the attack vector to privileged users. OCFS2 is not enabled by default in typical enterprise installations and is primarily deployed within specialized clustering setups. Furthermore, triggering the flaw depends on encountering a specific failure path during quota initialization, limiting the practical outcome to a local denial of service via a kernel panic.

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.