CVE-2026-22992

Description

A flaw was found in the Linux kernel's Ceph network client module (libceph). When establishing a secure connection, the client does not properly handle errors reported during the authentication phase, allowing background session establishment to proceed in an invalid state. A malicious or compromised storage monitor can exploit this flaw to trigger an invalid memory access (NULL pointer dereference) during signature verification, leading to a kernel crash and Denial of Service (DoS).

Statement

The monitor auth-done handler incorrectly returned success even when the authentication reply finalization reported an error, causing a state mismatch where msgr2 could continue session establishment in the background. In secure mode this can trigger a WARN and later a NULL pointer dereference in signature preparation, leading to a remote crash/DoS (network-reachable under a malicious/compromised monitor or MITM conditions).

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 Score6.55.57.5
Attack VectorAdjacent NetworkLocalNetwork
Attack ComplexityLowLowLow
Privileges RequiredNoneLowNone
User InteractionNoneNoneNone
ScopeUnchangedUnchangedUnchanged
ConfidentialityNoneNoneNone
Integrity ImpactNoneNoneNone
Availability ImpactHighHighHigh

Vector

Red Hat: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

NVD: 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,Integrity

Technical Impact: Unexpected State; Varies by Context; DoS: Crash, Exit, or Restart

The product could be prevented from detecting unexpected states and conditions, placing the product into a state that could lead to a crash or other unintended behaviors.

Access Control

Technical Impact: Bypass Protection Mechanism

If the method/function is used for a protection mechanism, then an unchecked return value could prevent the code from being able to see if the protection mechanism fails. For example, if the program calls a function to drop privileges but does not check the return code to ensure that privileges were successfully dropped, then the program will continue to operate with the higher privileges.

Frequently Asked Questions

Want to get errata notifications? Sign up here.