CVE-2026-99590

Description

A flaw was found in the Linux kernel's Ceph file system client. This flaw allows a malicious or compromised Metadata Server (MDS) to cause kernel memory corruption or a Denial of Service (DoS) via an out-of-bounds write. When processing inline data received from the server, the client does not verify that the data fits into the allocated memory buffer, causing it to write past the end of the buffer.

Statement

This vulnerability is rated as Important because an attacker controlling or impersonating a Ceph Metadata Server could trigger kernel memory corruption or cause a system crash on client systems. Red Hat Enterprise Linux systems are only exposed if the Ceph filesystem kernel module is loaded and actively mounting a CephFS share from an untrusted or compromised cluster. Environments that do not use the in-kernel CephFS client, or that only connect to fully trusted infrastructure, have significantly lower operational risk.

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 Score8.1N/AN/A
Attack VectorNetworkN/AN/A
Attack ComplexityHighN/AN/A
Privileges RequiredNoneN/AN/A
User InteractionNoneN/AN/A
ScopeUnchangedN/AN/A
ConfidentialityHighN/AN/A
Integrity ImpactHighN/AN/A
Availability ImpactHighN/AN/A

Vector

Red Hat: CVSS:3.1/AV:N/AC:H/PR:N/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.