Skip to main content

Linux Kernel libceph CVE-2026-68433

| EUVDEUVD-2026-57041 HIGH
2026-08-12 Linux GHSA-w6pj-fv9f-22wf
8.6
CVSS 3.1 · Vendor: Linux
Share

Severity by source

Vendor (Linux) PRIMARY
8.6 HIGH
AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:H
vuln.today AI
6.5 MEDIUM

AC:H because exploiting requires network position (rogue monitor or MITM); I:N because uninitialized read confers no write/integrity impact.

3.1 AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:H
4.0 AV:N/AC:H/AT:N/PR:N/UI:N/VC:L/VI:N/VA:H/SC:N/SI:N/SA:N
SUSE
5.5 MEDIUM
AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Red Hat
5.5 MEDIUM
qualitative

Primary rating from Vendor (Linux).

CVSS VectorVendor: Linux

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
High

Lifecycle Timeline

5
Analysis Generated
Aug 14, 2026 - 01:54 vuln.today
CVSS changed
Aug 13, 2026 - 23:37 NVD
8.6 (HIGH)
Patch available
Aug 12, 2026 - 01:02 EUVD
CVE Published
Aug 12, 2026 - 00:07 cve.org
UNKNOWN (no severity yet)
CVE Published
Aug 12, 2026 - 00:07 cve.org
HIGH 8.6

DescriptionCVE.org

In the Linux kernel, the following vulnerability has been resolved:

libceph: bound get_version reply decode to front len

handle_get_version_reply() uses msg->front_alloc_len as the decode boundary for MON_GET_VERSION_REPLY. That is the size of the reused reply buffer, not the number of bytes actually received.

A truncated reply can therefore pass ceph_decode_need() and decode the second u64 from stale tail bytes left in the buffer by an earlier message, causing an uninitialized memory read.

Use msg->front.iov_len as the receive-side decode boundary, matching other libceph reply handlers and limiting decoding to the bytes that were actually read from the wire.

AnalysisAI

Uninitialized memory read in the Linux kernel's libceph client library exposes stale kernel buffer contents and risks system instability on Ceph-connected hosts. The flaw exists in handle_get_version_reply(), which incorrectly uses msg->front_alloc_len - the allocated buffer size - as the decode boundary instead of msg->front.iov_len, the count of bytes actually received. A truncated MON_GET_VERSION_REPLY from a malicious or compromised Ceph monitor therefore passes the ceph_decode_need() guard and reads a second u64 from leftover bytes of a prior message, constituting an out-of-bounds read of uninitialized kernel memory. No public exploit has been identified at time of analysis, but the 16% EPSS score is elevated for a kernel library flaw and warrants prompt patching on Ceph-client deployments.

Technical ContextAI

libceph is the in-kernel Ceph client library (drivers/block/rbd.c, net/ceph/) that implements the Ceph wire protocol between Linux clients and Ceph monitor/OSD clusters. MON_GET_VERSION_REPLY is a monitor reply message used to synchronize version numbers between client and monitor. The reply decode path in handle_get_version_reply() uses msg->front_alloc_len - a fixed allocation size representing the largest possible reused buffer - as the upper boundary passed to ceph_decode_need(). When a truncated reply arrives, front.iov_len (actual received bytes) is smaller than front_alloc_len, so the bounds check incorrectly permits a read into stale tail bytes from a prior message that occupied the same buffer. This is an instance of CWE-125 (Out-of-Bounds Read) combined with CWE-908 (Use of Uninitialized Resource): the second u64 decoded may contain kernel heap residue from an earlier network message. The fix aligns this handler with other libceph reply decoders by substituting front.iov_len for front_alloc_len, confining decodes strictly to received data.

RemediationAI

The primary remediation is upgrading to a patched kernel version: 6.6.148 or later on the 6.6 LTS branch, 6.12.101 or later on the 6.12 branch, 6.18.42 or later on the 6.18 branch, 7.1.6 or later on the 7.1 branch, or 7.2-rc5 or later on mainline. Upstream stable commits are published at https://git.kernel.org/stable/c/ under the hashes listed in references. Distribution users should apply their vendor's kernel update as soon as it incorporates these backports. As a compensating control where patching is not immediately possible, limiting network access to Ceph monitor ports (default TCP 6789 and v2 port 3300) from untrusted network segments reduces the attack surface; this prevents a rogue external monitor from sending crafted replies but does not protect against a compromised internal monitor. Disabling libceph entirely (removing rbd and ceph kernel modules) eliminates the vulnerable code path entirely at the cost of losing Ceph storage access. No workarounds address the root cause; patch as the definitive fix.

Vendor StatusVendor

SUSE

Severity: Moderate
Product Status
SUSE Linux Enterprise Desktop 15 SP7 Affected
SUSE Linux Enterprise Desktop 15 SP7 Affected
SUSE Linux Enterprise High Availability Extension 15 SP7 Affected
SUSE Linux Enterprise High Availability Extension 15 SP7 Affected
SUSE Linux Enterprise High Availability Extension 16.0 Affected

Share

CVE-2026-68433 vulnerability details – vuln.today

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy